public inbox for linux-rockchip@lists.infradead.org
 help / color / mirror / Atom feed
From: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
To: Jagan Teki <jagan@amarulasolutions.com>,
	Simon Glass <sjg@chromium.org>,
	Philipp Tomsich <philipp.tomsich@theobroma-systems.com>,
	Kever Yang <kever.yang@rock-chips.com>,
	Akash Gajjar <akash@openedev.com>
Cc: linux-rockchip@lists.infradead.org,
	linux-amarula <linux-amarula@amarulasolutions.com>,
	U-Boot-Denx <u-boot@lists.denx.de>
Subject: Re: [PATCH v3 03/13] rockchip: dts: rk3399: Create initial rk3399-u-boot.dtsi
Date: Fri, 26 Apr 2019 15:33:10 +0200	[thread overview]
Message-ID: <74b318c7981129280a7ea5ce1bf9426360b8459b.camel@bootlin.com> (raw)
In-Reply-To: <CAMty3ZAoTizHUXXAwKXov2SBVYFQfQj2rrSm1zK2i08O+wpdfQ@mail.gmail.com>

Hi,

On Fri, 2019-04-26 at 18:51 +0530, Jagan Teki wrote:
> On Thu, Apr 25, 2019 at 11:04 PM Jagan Teki <jagan@amarulasolutions.com> wrote:
> > u-boot,dm-pre-reloc is required for SDMMC booted rk3399 boards and
> > which is U-Boot specific devicetrees binding.
> > 
> > Move it on global rk3399-u-boot.dtsi file and rest of the U-Boot
> > bindings will move it future based on the requirement.
> > 
> > This would help to sync the devicetrees from Linux whenever required
> > instead of adding specific nodes.
> > 
> > Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> > Reviewed-by: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
> > ---
> >  arch/arm/dts/rk3399-evb.dts     | 1 -
> >  arch/arm/dts/rk3399-firefly.dts | 1 -
> >  arch/arm/dts/rk3399-puma.dtsi   | 1 -
> >  arch/arm/dts/rk3399-u-boot.dtsi | 8 ++++++++
> >  4 files changed, 8 insertions(+), 3 deletions(-)
> >  create mode 100644 arch/arm/dts/rk3399-u-boot.dtsi
> > 
> > diff --git a/arch/arm/dts/rk3399-evb.dts b/arch/arm/dts/rk3399-evb.dts
> > index ce004d0d18..9162f3dd50 100644
> > --- a/arch/arm/dts/rk3399-evb.dts
> > +++ b/arch/arm/dts/rk3399-evb.dts
> > @@ -155,7 +155,6 @@
> >  };
> > 
> >  &sdmmc {
> > -       u-boot,dm-pre-reloc;
> >         bus-width = <4>;
> >         status = "okay";
> >  };
> > diff --git a/arch/arm/dts/rk3399-firefly.dts b/arch/arm/dts/rk3399-firefly.dts
> > index f90e7e88db..46f2ffaf8d 100644
> > --- a/arch/arm/dts/rk3399-firefly.dts
> > +++ b/arch/arm/dts/rk3399-firefly.dts
> > @@ -592,7 +592,6 @@
> >  };
> > 
> >  &sdmmc {
> > -       u-boot,dm-pre-reloc;
> >         bus-width = <4>;
> >         status = "okay";
> >  };
> > diff --git a/arch/arm/dts/rk3399-puma.dtsi b/arch/arm/dts/rk3399-puma.dtsi
> > index 8304f67192..9049694243 100644
> > --- a/arch/arm/dts/rk3399-puma.dtsi
> > +++ b/arch/arm/dts/rk3399-puma.dtsi
> > @@ -492,7 +492,6 @@
> >  };
> > 
> >  &sdmmc {
> > -       u-boot,dm-pre-reloc;
> 
> We need to explicitly include rk3399-u-boot.dtsi to these files since
> the SoC name is rockchip, I'm sending other series for these changes.
> and I have send v3.1 patches for only this change [1] and rest
> unchanged.

Does this mean that the rk3399-u-boot.dtsi file won't be auto-included
from the boards dtsi? If so, we should probably create -u-boot.dtsi
files for each device, to include rk3399-u-boot.dtsi.

Cheers,

Paul

> Sorry for not noticing before.
> 
> [1] https://patchwork.ozlabs.org/patch/1091534/
-- 
Paul Kocialkowski, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com

_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

  reply	other threads:[~2019-04-26 13:33 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 17:34 [PATCH v3 00/13] rockchip: Add new rk3399 boards Jagan Teki
     [not found] ` <20190425173427.13445-1-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2019-04-25 17:34   ` [PATCH v3 01/13] rockchip: dts: rk3399: Sync rk3399-opp from Linux Jagan Teki
2019-04-25 17:34   ` [PATCH v3 02/13] rockchip: dts: rk3399: Sync pwm2_pin_pull_down from Linux 5.1-rc2 Jagan Teki
2019-04-25 17:34   ` [PATCH v3 03/13] rockchip: dts: rk3399: Create initial rk3399-u-boot.dtsi Jagan Teki
     [not found]     ` <20190425173427.13445-4-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2019-04-26 13:21       ` Jagan Teki
2019-04-26 13:33         ` Paul Kocialkowski [this message]
2019-04-25 17:34   ` [PATCH v3 04/13] Kconfig: Add default SPL_FIT_GENERATOR for rockchip Jagan Teki
2019-04-25 17:34   ` [PATCH v3 05/13] arm: rockchip: rk3399: Move common configs in Kconfig Jagan Teki
2019-04-25 17:34   ` [PATCH v3 06/13] rockchip: rk3399: Add Orangepi RK3399 support Jagan Teki
2019-04-26 14:17     ` Paul Kocialkowski
     [not found]       ` <51dab1c2fea1ca16b892c9face5fd4c6b451d07d.camel-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org>
2019-04-26 14:27         ` Jagan Teki
2019-04-26 14:34           ` Paul Kocialkowski
     [not found]             ` <f89a6bbc7390db5f9ed6f7ad732b6451cdea15c4.camel-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org>
2019-04-26 14:45               ` Jagan Teki
2019-04-26 14:54                 ` Paul Kocialkowski
     [not found]                   ` <5953e5f8b8d45cdc5c208c75b16e831391f3db08.camel-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org>
2019-04-26 15:01                     ` Jagan Teki
2019-04-26 15:12                       ` Paul Kocialkowski
2019-04-26 15:18                         ` Jagan Teki
2019-04-26 15:38                           ` Paul Kocialkowski
2019-04-26 15:48                             ` Jagan Teki
2019-04-26 16:08                               ` Paul Kocialkowski
2019-04-26 16:09                                 ` Philipp Tomsich
     [not found]                                 ` <d5d26a75416da7249f21517e080cff2309393dfe.camel-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org>
2019-04-26 16:16                                   ` Jagan Teki
2019-04-26 16:40                                     ` Paul Kocialkowski
2019-04-26 16:53                                       ` Jagan Teki
2019-04-26 17:08                                         ` Paul Kocialkowski
2019-04-26 17:21                                           ` Jagan Teki
2019-04-26 17:37                                             ` Paul Kocialkowski
     [not found]                                               ` <e1fad022ad1407df514ab8fd4d44485cf3e4f82a.camel-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org>
2019-04-26 17:42                                                 ` Jagan Teki
2019-04-26 18:02                                                   ` Paul Kocialkowski
2019-04-25 17:34   ` [PATCH v3 07/13] rockchip: dts: rk3399: Sync rk3399-nanopi4.dtsi from Linux Jagan Teki
2019-04-25 17:34   ` [PATCH v3 08/13] rockchip: dts: rk3399: nanopi4: Use CD pin as RK_FUNC_1 Jagan Teki
2019-04-25 17:34   ` [PATCH v3 09/13] rockchip: rk3399: Add Nanopi M4 board support Jagan Teki
2019-04-25 17:34   ` [PATCH v3 10/13] rockchip: rk3399: Add Nanopi NEO4 " Jagan Teki
2019-04-25 17:34   ` [PATCH v3 11/13] rockchip: rk3399: Add Rockpro64 " Jagan Teki
2019-04-25 17:34   ` [PATCH v3 12/13] rockchip: rk3399: Add Rock PI 4 support Jagan Teki
2019-04-25 17:34   ` [PATCH v3 13/13] doc: rockchip: Add global doc for rk3399 build/flash Jagan Teki

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=74b318c7981129280a7ea5ce1bf9426360b8459b.camel@bootlin.com \
    --to=paul.kocialkowski@bootlin.com \
    --cc=akash@openedev.com \
    --cc=jagan@amarulasolutions.com \
    --cc=kever.yang@rock-chips.com \
    --cc=linux-amarula@amarulasolutions.com \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=philipp.tomsich@theobroma-systems.com \
    --cc=sjg@chromium.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox