From: Artturi Alm <artturi.alm@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] rk3xxx.dtsi /usb_host missing specific compatible
Date: Sat, 26 Aug 2017 22:15:26 +0300 [thread overview]
Message-ID: <20170826191526.GA59434@gmail.com> (raw)
In-Reply-To: <5652869.dcIyx1TKc9@phil>
On Sat, Aug 26, 2017 at 07:48:28PM +0200, Heiko Stuebner wrote:
> Am Freitag, 25. August 2017, 13:20:47 CEST schrieb Philipp Tomsich:
> > + Heiko
> >
> > On Wed, 23 Aug 2017, Artturi Alm wrote:
> >
> > > Hi,
> > >
> > >
> > > no idea if this is the right place to mail about this, but i got
> > > suggested this node is out-of-norm, and the diff below fixes that
> > > for me on rk3188.
> > >
> > > -Artturi
> >
> > When submitting changes, please send a patch w/ an appropriate commit
> > message (e.g. using patman). If you tag it as "rockchip:", it will
> > eventually get assigned to my queue.
> >
> > >
> > > diff --git a/arch/arm/dts/rk3xxx.dtsi b/arch/arm/dts/rk3xxx.dtsi
> > > index 6d9e36d235..21f2afc104 100644
> > > --- a/arch/arm/dts/rk3xxx.dtsi
> > > +++ b/arch/arm/dts/rk3xxx.dtsi
> > > @@ -157,7 +157,7 @@
> > > };
> > >
> > > usb_host: usb at 101c0000 {
> > > - compatible = "snps,dwc2";
> > > + compatible = "rockchip,rk3066-usb", "snps,dwc2";
> >
> > This is the same on the Linux upstream, which is the leading repository
> > for this DTS file. Also, the "rockchip,rk3066-usb" is used by none of the
> > drivers (whereas "snsp,dwc2" is matche by drivers/usb/host/dwc2.c.
> >
> > From my point of view, there's no point in changing this (unless Heiko
> > would like to see this changed both here and in Linux).
>
> In general it is common practice to have a more specialized compatible
> as a reserve, to be able add "quirks" later on if necessary without needing
> devicetree updates as well. For example the otg node does already have
> the rk3066-usb compatible.
>
> On the kernel-side, we even do have specialized init values for Rockchip
> dwc2 controllers, which is bound to the rk3066-usb compatible. I'm not
> sure why only the otg controller got it though and the addition of the
> dwc2 nodes in the mainline kernel was already in 2014 :-) .
>
> So I don't have a set opinion one way or another, as it looks like things
> work reasonably well as they are now, but if someone sends in a
> _tested_ kernel patch setting the specific compatible, I'll look at it
> and possibly apply it :-) .
>
>
> Heiko
I was asking this for OpenBSD actually, as it has these FDT
"attachment-drivers" via rather generic stubs to do the driver attachment
with compatibles alone for matching the needed config.
I've already worked around, but think of it as ugly SoC-specific hack as-is.
Hmmph, i missed a detail before, i might actually need this fixed in Linux too.
I haven't seen any patches to .dts files in the OpenBSD-ports package,
for the .dtb files shipped for use, and iirc they're sourced from Linux.
I'll leave the tested linux patch for a very rainy day, because atm. u-boot is
broken enough on rk3188 that i can't really test anything on them.
-Artturi
prev parent reply other threads:[~2017-08-26 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 21:39 [U-Boot] rk3xxx.dtsi /usb_host missing specific compatible Artturi Alm
2017-08-25 11:20 ` Philipp Tomsich
2017-08-26 17:48 ` Heiko Stuebner
2017-08-26 19:15 ` Artturi Alm [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=20170826191526.GA59434@gmail.com \
--to=artturi.alm@gmail.com \
--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