From: Roger Quadros <rogerq@kernel.org>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: nm@ti.com, vigneshr@ti.com, afd@ti.com, kristo@kernel.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, srk@ti.com, r-gunasekaran@ti.com,
b-liu@ti.com, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 5/5] arm64: dts: ti: k3-am62*: Add PHY2 region to USB wrapper node
Date: Fri, 12 Apr 2024 14:39:56 +0300 [thread overview]
Message-ID: <81aaa055-f095-498c-97dd-aee10816a132@kernel.org> (raw)
In-Reply-To: <20240408095200.GA14655@francesco-nb>
Hi Francesco,
On 08/04/2024 12:52, Francesco Dolcini wrote:
> Hello Roger,
>
> On Thu, Feb 01, 2024 at 02:03:32PM +0200, Roger Quadros wrote:
>> Add PHY2 register space to USB wrapper node. This is required
>> to deal with Errata i2409.
>>
>> Signed-off-by: Roger Quadros <rogerq@kernel.org>
>
> What's the status/plan for this? v6.9-rc misses it and therefore we have
> this error in the logs (and of course, we miss the workaround).
I will send the fix for this for v6.9+.
>
> [ 0.583305] dwc3-am62 f910000.dwc3-usb: invalid resource (null)
> [ 0.589304] dwc3-am62 f910000.dwc3-usb: can't map PHY IOMEM resource. Won't apply i2409 fix.
>
> Apart for the error message, the change here seems required for the
> hardware to properly function (IOW IMHO it should be back-ported to stable).
>
> Francesco
>
--
cheers,
-roger
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-04-12 11:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 12:03 [PATCH v3 0/5] arm64: dts: ti: am62: Add USB support for k3-am62p Roger Quadros
2024-02-01 12:03 ` [PATCH v3 1/5] dt-bindings: mfd: syscon: Add ti,am62-usb-phy-ctrl compatible Roger Quadros
2024-02-02 20:26 ` Rob Herring
2024-02-01 12:03 ` [PATCH v3 2/5] arm64: dts: ti: k3-am62/a: use sub-node for USB_PHY_CTRL registers Roger Quadros
2024-02-01 15:23 ` Andrew Davis
2024-02-01 12:03 ` [PATCH v3 3/5] arm64: dts: ti: k3-am62p: add the USB sub-system Roger Quadros
2024-02-01 12:03 ` [PATCH v3 4/5] dt-bindings: usb/ti,am62-usb.yaml: Add PHY2 register space Roger Quadros
2024-02-01 18:15 ` Conor Dooley
2024-02-01 18:18 ` Conor Dooley
2024-02-01 18:35 ` Bin Liu
2024-02-01 19:13 ` Conor Dooley
2024-02-02 9:36 ` Roger Quadros
2024-02-02 9:53 ` Conor Dooley
2024-02-02 10:13 ` Roger Quadros
2024-02-02 12:18 ` Nishanth Menon
2024-02-02 13:59 ` Roger Quadros
2024-02-02 14:59 ` Nishanth Menon
2024-02-02 16:39 ` Conor Dooley
2024-02-14 11:27 ` [PATCH v3 5/5] usb: dwc3-am62: add workaround for Errata i2409 Andrejs Cainikovs
2024-02-01 12:03 ` [PATCH v3 5/5] arm64: dts: ti: k3-am62*: Add PHY2 region to USB wrapper node Roger Quadros
2024-04-08 9:52 ` Francesco Dolcini
2024-04-12 11:39 ` Roger Quadros [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=81aaa055-f095-498c-97dd-aee10816a132@kernel.org \
--to=rogerq@kernel.org \
--cc=afd@ti.com \
--cc=b-liu@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=francesco@dolcini.it \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=r-gunasekaran@ti.com \
--cc=robh+dt@kernel.org \
--cc=srk@ti.com \
--cc=vigneshr@ti.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).