From: Tony Lindgren <tony@atomide.com>
To: Oskar Holmlund <info@ohdata.se>
Cc: linux-omap@vger.kernel.org, bcousson@baylibre.com
Subject: Re: PATCH: ARM: am33xx.dtsi USB ranges length
Date: Mon, 8 Jun 2020 09:55:26 -0700 [thread overview]
Message-ID: <20200608165526.GI37466@atomide.com> (raw)
In-Reply-To: <d22deb609cf4678d569928f4a48cb409@ohdata.se>
* Oskar Holmlund <info@ohdata.se> [200605 17:46]:
> AM335x TRM: Table 2-1 defines USBSS - USB Queue Manager in memory region
> 0x4740 0000 to 0x4740 7FFF.
Oh OK, looks like the older TRM revisions list the ragen from
offset 0x5000 to 0x8000 as reserved. Thanks for fixing it,
applying into fixes.
BTW, you should check your setup and use git tools for
generating the patches. I could not git am apply it directly
without manual editing. And then scripts/checkpatch_pl --strict
still complained as you have different sender email from
commit email. With git this gets fixed up with an extra
"From:" at the top of the email.
Regards,
Tony
> Diff created from am33xx.dtsi commit
> e20ef23dd6937c38df2cfddf15270668153c8177
>
> Signed-off-by: Oskar Holmlund <oskar@ohdata.se>
> --- arch/arm/boot/dts/am33xx.dtsi.orig 2020-06-05 18:58:39.720383275 +0200
> +++ arch/arm/boot/dts/am33xx.dtsi 2020-06-05 19:01:32.974619980 +0200
> @@ -347,7 +347,7 @@
> clock-names = "fck";
> #address-cells = <1>;
> #size-cells = <1>;
> - ranges = <0x0 0x47400000 0x5000>;
> + ranges = <0x0 0x47400000 0x8000>;
>
> usb0_phy: usb-phy@1300 {
> compatible = "ti,am335x-usb-phy";
>
> --
> Bästa Hälsningar
> Oskar Holmlund
> Tel 070-3220292
prev parent reply other threads:[~2020-06-08 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 17:49 PATCH: ARM: am33xx.dtsi USB ranges length Oskar Holmlund
2020-06-08 16:55 ` Tony Lindgren [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=20200608165526.GI37466@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=info@ohdata.se \
--cc=linux-omap@vger.kernel.org \
/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).