From: Scott Wood <scottwood@freescale.com>
To: Nikhil Badola <nikhil.badola@freescale.com>
Cc: devicetree@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc: dts: t208x: Change T208x USB controller version
Date: Thu, 21 Aug 2014 17:36:33 -0500 [thread overview]
Message-ID: <1408660593.6510.0.camel@snotra.buserror.net> (raw)
In-Reply-To: <1408617090-29692-1-git-send-email-nikhil.badola@freescale.com>
On Thu, 2014-08-21 at 16:01 +0530, Nikhil Badola wrote:
> Change USB controller version to 2.5 in compatible string for T2080/T2081
>
> Signed-off-by: Nikhil Badola <nikhil.badola@freescale.com>
> ---
> Checkpatch warnings handled by commit 61a8c2c6fe71082de3ea8629589dcdd0cc5c3f02
That checkpatch warning is known to have false positives in cases where
the binding says "<CHIPNAME>-device" or "device-<VERSION>". If you want
to update the binding to give an example with a version, that's fine,
but checkpatch shouldn't be why. We're not going to update the binding
example again to match a different version the next time one is added to
a device tree...
> Documentation: dts: fsl-usb: Document USB node compatible string for IP version
>
> arch/powerpc/boot/dts/fsl/t2081si-post.dtsi | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/powerpc/boot/dts/fsl/t2081si-post.dtsi b/arch/powerpc/boot/dts/fsl/t2081si-post.dtsi
> index 97479f0..aecee96 100644
> --- a/arch/powerpc/boot/dts/fsl/t2081si-post.dtsi
> +++ b/arch/powerpc/boot/dts/fsl/t2081si-post.dtsi
> @@ -410,7 +410,7 @@
> /include/ "qoriq-gpio-3.dtsi"
> /include/ "qoriq-usb2-mph-0.dtsi"
> usb0: usb@210000 {
> - compatible = "fsl-usb2-mph-v2.4", "fsl-usb2-mph";
> + compatible = "fsl-usb2-mph-v2.5", "fsl-usb2-mph";
This is an example of why it's better to rely on version registers when
present.
-Scott
next prev parent reply other threads:[~2014-08-21 22:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 10:31 [PATCH] powerpc: dts: t208x: Change T208x USB controller version Nikhil Badola
2014-08-21 22:36 ` Scott Wood [this message]
2014-09-10 4:45 ` nikhil.badola
2014-09-10 5:16 ` Scott Wood
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=1408660593.6510.0.camel@snotra.buserror.net \
--to=scottwood@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nikhil.badola@freescale.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;
as well as URLs for NNTP newsgroup(s).