public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Xavier Drudis Ferran <xdrudis@tinet.cat>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: "Xavier Drudis Ferran" <xdrudis@tinet.cat>,
	u-boot@lists.denx.de, "Simon Glass" <sjg@chromium.org>,
	"Philipp Tomsich" <philipp.tomsich@vrull.eu>,
	"Lukasz Majewski" <lukma@denx.de>,
	"Sean Anderson" <seanga2@gmail.com>,
	"Marek Vasut" <marex@denx.de>, 吴良峰 <william.wu@rock-chips.com>
Subject: Re: [PATCH] arm: dts: rockchip: rk3399: usb: ehci: Fix EHCI probe in rk3399 to access peripherals by USB 2.
Date: Wed, 31 Aug 2022 10:02:47 +0200	[thread overview]
Message-ID: <Yw8Vp7RIQLZomMjW@begut> (raw)
In-Reply-To: <6b1207ad-51d0-f609-3fb6-7f12d70902d7@rock-chips.com>

El Sat, Aug 27, 2022 at 11:20:17AM +0800, Kever Yang deia:
> The idea for dtsi now is to sync the kernel and U-Boot dts, and Linux
> distribution will
> use the dts from U-Boot. If we change the dts property in -u-boot.dts, it
> will also pass
> to kernel, which make kernel function not available. So we would like to
> sync the driver
> for kernel and u-boot to use the same dts nodes.
>

That's news to me. I was thinking all the time that the reason for having 
some dtsi? files with -u-boot suffix was that these were exclusive for u-boot
and the others were shared with linux. If now the content of .*-u-boot.dtsi? 
gets passed to linux too, I no longer know why we separate the files.
Is this for Rockchip or ARM64 or a general rule for all of U-Boot? 
Should I (or someone) try to change documentation or is that already done?
I thought I read something different few months ago ? Maybe I misunderstood...

> So we can try option 1, output warning instead of error return for clock get
> fail, since the clock
> driver for kernel and u-boot are totally different.
> 

Ok. I hope I find time to try that some day. 

Thanks for looking at the patch.

      reply	other threads:[~2022-08-31  8:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01 18:59 [PATCH] arm: dts: rockchip: rk3399: usb: ehci: Fix EHCI probe in rk3399 to access peripherals by USB 2 Xavier Drudis Ferran
2022-07-15 19:34 ` Xavier Drudis Ferran
2022-08-27  3:20 ` Kever Yang
2022-08-31  8:02   ` Xavier Drudis Ferran [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=Yw8Vp7RIQLZomMjW@begut \
    --to=xdrudis@tinet.cat \
    --cc=kever.yang@rock-chips.com \
    --cc=lukma@denx.de \
    --cc=marex@denx.de \
    --cc=philipp.tomsich@vrull.eu \
    --cc=seanga2@gmail.com \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    --cc=william.wu@rock-chips.com \
    /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