[PATCH 1/3] arm: Add support for Qualcomm IPQ40xx family

[Tom Rini]

On Fri, Jul 10, 2020 at 07:31:34PM +0200, Robert Marko wrote:
> On Fri, Jul 10, 2020 at 6:57 PM Tom Rini <trini at konsulko.com> wrote:
> >
> > On Fri, Jul 10, 2020 at 05:52:51PM +0200, Robert Marko wrote:
> > > On Fri, Jul 10, 2020 at 5:25 PM Tom Rini <trini at konsulko.com> wrote:
> > >
> > > > On Mon, Jul 06, 2020 at 10:37:54AM +0200, Robert Marko wrote:
> > > >
> > > > > This introduces initial support for the popular Qualcomm
> > > > > IPQ40x8 and IPQ40x9 WiSoC series.
> > > > >
> > > > > IPQ40xx series have 4x Cortex A7 ARM-v7A cores.
> > > > > Supported are: IPQ4018, IPQ4019, IPQ4028 and IPQ4029.
> > > > >
> > > > > IPQ40x8 and IPQ40x9 use the same cores, but differ in
> > > > > addressable RAM size (1GB for IPQ40x9 and 256MB for IPQ40x8)
> > > > > and supported peripherals (IPQ40x8 lacks RGMII, LCD controller
> > > > > and EMMC/SDHCI controllers).
> > > > >
> > > > > IQP4028/IPQ4029 models differ from IPQ4018/IPQ4019 only
> > > > > by their rated temperatures rates with IPQ402X models being
> > > > > rated for wider temperature ranges.
> > > > >
> > > > > Initially this supports:
> > > > > * Simple clock driver (Only for UART1 now, will be extended)
> > > > > * Pinctrl driver (Supports UARTX and GPIO now, will be extended)
> > > > > * GPIOs already supported by msm_gpio driver with updates
> > > > > * UARTs already supported by serial_msm driver with updates
> > > > >
> > > > > Further peripherals will come in later patches.
> > > > >
> > > > > Signed-off-by: Robert Marko <robert.marko at sartura.hr>
> > > > > ---
> > > > >  MAINTAINERS                                |   7 ++
> > > > >  arch/arm/Kconfig                           |  13 ++
> > > > >  arch/arm/Makefile                          |   1 +
> > > > >  arch/arm/dts/qcom-ipq4019.dtsi             |  79 ++++++++++++
> > > >
> > > > The goal with dts files (that aren't the -u-boot.dtsi ones of course) is
> > > > that they come from upstream Linux.  How far along is that with this
> > > > SoC?  Everything else here looks fine, thanks.
> > > >
> > > Well, I tried to keep as much as possible identical or really similar to
> > > the upstream Linux nodes,
> > > but there are still differences due to how drivers are simplified.
> >
> > OK.  You should be able to take the base upstream DTS files and between
> > things like CONFIG_OF_REMOVE_PROPS / CONFIG_OF_SPL_REMOVE_PROPS and the
> > automatically included -u-boot.dtsi files make any further changes that
> > we have to make for space reasons or other tweaks.
>
> Well, I would actually like to avoid that kind of scenario as Linux
> DTS has way more nodes that U-boot will ever have.
> I intentionally used the smallest possible amount of DT nodes that made sense.

That's the opposite of the current intentions.  But so long as all of
the bindings you're using match, at the end of the day the additional
maintenance is on you, so it's not a blocker for merging.  Thanks for
explaining.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200710/b7e2f890/attachment.sig>