All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan B. <stefan_b@posteo.net>
To: u-boot@lists.denx.de
Subject: [RFC PATCH 00/10] arm: add support for SoC S5P4418
Date: Tue, 25 Feb 2020 20:13:57 +0100	[thread overview]
Message-ID: <0ee107e2-6fa3-7c03-cce8-0e857566b466@posteo.net> (raw)
In-Reply-To: <CABHD4K-CUwkRwZM=1WHJ4A_YveYNXtyowKHretWKB+ZyK1gJtg@mail.gmail.com>

Hi Amit,

Am 22.02.20 um 14:06 schrieb Amit Tomer:
> Hi,
> 
> On Tue, Feb 4, 2020 at 1:12 AM Stefan Bosch <stefan_b@posteo.net> wrote:
>>
>>
>> This patch adds support for SAMSUNG's/NEXELL's ARM Cortex-A9 based
>> S5P4418 SoC, especially FriendlyARM's NanoPi2 and NanoPC-T2 boards.
>> It is based on the following FriendlyARM's U-Boot version:
>> https://github.com/friendlyarm/u-boot/tree/nanopi2-v2016.01.
>>
> I don't think this is the right approach, i.e. to take everything from
> BSP source as it is and put
> it into mainline U-BOOT. AFAIR,  Some of the peripherals present on
> these NEXELL SoC's are
> compatible with SAMSUNG IP (for instance the UART).
> So, are we sure that some of the already existing code in U-BOOT can't
> be re-used to drive those
> compatible peripherals at-least ?
> 
> Thanks
> -Amit
> 

You are right, already existing code in U-BOOT should be used where 
possible. So I have reviewed the code (and will review it further). Up 
to now, I have the following proposals for the peripherials indicated:

UART:
Actually the UARTs of the S5P4418 are Amba PrimeCell PL011 compatible, 
therefore the appropriate code is used. S5P6818 does have different 
UARTs which apparently arch/arm/mach-nexell/serial.c is for. Since 
S5P6818 is not supported (yet) I will remove this file.

TIMER:
Currently arch/arm/mach-nexell/timer.c is used. I will try to use 
arch/arm/cpu/armv7/s5p-common/timer.c instead. The timer-registers used 
seem to be the same, but the functions in timer.c are not which is a 
possible pitfall.

PWM:
Currently drivers/pwm/pwm-nexell.c is used. This is a extended version 
of arch/arm/cpu/armv7/s5p-common/pwm.c. I.e. pwm.c is adapted with
"#if defined(CONFIG_ARCH_NEXELL) ... #else" at some places. So my 
proposal is to change s5p-common/pwm.c appropriately to get rid of 
pwm-nexell.c.


Regards
Stefan

      reply	other threads:[~2020-02-25 19:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-03 19:39 [RFC PATCH 00/10] arm: add support for SoC S5P4418 Stefan Bosch
2020-02-03 20:32 ` [RFC PATCH 01/10] arm: add mach-nexell (header files) Stefan Bosch
2020-02-03 20:38 ` [RFC PATCH 02/10] arm: add mach-nexell (all files except header files) Stefan Bosch
2020-02-03 20:40 ` [RFC PATCH 03/10] i2c: mmc: add nexell driver (gpio, i2c, mmc, pwm) Stefan Bosch
2020-02-04  6:58   ` Heiko Schocher
2020-02-04 18:29     ` Stefan B.
2020-02-20 17:49     ` Stefan B.
2020-02-22 12:34       ` Heiko Schocher
2020-02-03 20:41 ` [RFC PATCH 04/10] video: add nexell video driver (soc: displaytop) Stefan Bosch
2020-02-03 20:43 ` [RFC PATCH 05/10] video: add nexell video driver (soc: mlc, mipi) Stefan Bosch
2020-02-03 20:44 ` [RFC PATCH 06/10] video: add nexell video driver (soc: lvds, hdmi) Stefan Bosch
2020-02-03 20:45 ` [RFC PATCH 07/10] video: add nexell video driver (soc: dpc, makefile) Stefan Bosch
2020-02-03 20:45 ` [RFC PATCH 08/10] video: add nexell video driver (display/video driver) Stefan Bosch
2020-02-03 20:46 ` [RFC PATCH 09/10] arm: add support for SoC s5p4418 (cpu) / nanopi2 board Stefan Bosch
2020-02-07 16:10   ` Tom Rini
2020-02-03 20:47 ` [RFC PATCH 10/10] arm: add (default) config for " Stefan Bosch
2020-02-07 16:11 ` [RFC PATCH 00/10] arm: add support for SoC S5P4418 Tom Rini
2020-02-22 13:06 ` Amit Tomer
2020-02-25 19:13   ` Stefan B. [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0ee107e2-6fa3-7c03-cce8-0e857566b466@posteo.net \
    --to=stefan_b@posteo.net \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.