From: Neil Armstrong <neil.armstrong@linaro.org>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Pierre-Olivier Mercier <nemunaire@nemunai.re>
Cc: Kevin Hilman <khilman@baylibre.com>,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org
Subject: Re: [BISECTED] arm64: dts: meson-sm1-odroid-hc4: USB not working
Date: Mon, 2 Jan 2023 10:50:38 +0100 [thread overview]
Message-ID: <b7dba825-3e39-fbf1-a73f-7e80a0d1bb5c@linaro.org> (raw)
In-Reply-To: <CAFBinCBaLLxO0ox9LJKS+LaQs4eqmtH_6Sbcv70rTLZz3b2qZg@mail.gmail.com>
On 27/12/2022 11:43, Martin Blumenstingl wrote:
> Hi Pierre-Olivier, Hi Neil,
>
> On Mon, Dec 26, 2022 at 11:48 PM Pierre-Olivier Mercier
> <nemunaire@nemunai.re> wrote:
>>
>> Hi,
>>
>> On my Odroid-HC4, the USB 2.0 port (the only one available) was not
>> working. While it seems I was not the only one in that case[1], after
>> some experiments, I found that by reverting the following commit:
>>
>> 703e84d6615a4 arm64: dts: meson-sm1-odroid-hc4: disable unused USB PHY0
> Thank you for bisecting the commit!
>
>> it solves the issue: USB is working on latest stable (6.1.1) with this
>> only patch reverted, while it doesn't with vanilla dtb (with same
>> config otherwise).
> [...]
>> I didn't read the specs, but I also tried to inverse the patch (disable
>> usb2_phy1 intead of usb2_phy0) and it didn't work neither. Apparently
>> usb2_phy0 and usb2_phy1 are both required for some reason...
> After reading this mail yesterday I could not make much sense of it.
> Now, while re-reading it I remembered the time when I worked on GXL
> USB support and wrote the following comment: [0]
> All USB2 PHYs (which are internally "connected" to the dwc3 roothub)
> need to be powered on, otherwise USB devices cannot be
> enumerated (even if just one PHY is disabled and if the device is
> plugged into another, enabled port)
>
> This is probably also the reason why I left all USB PHYs enabled by
> default in meson-{gxl,gxm}.dtsi (and so did we in
> meson-g12-common.dtsi). Instead we're disabling the &usb node by
> default (and enabling it for boards that have USB ports).
> For readers not familiar with the default enabled/disabled: typically
> we disable the nodes for IP blocks in the .dtsi and then each
> board.dts enables them on demand.
>
> Neil, what do you think about this?
> Should Pierre-Olivier send a formal revert (with the problem being
> described as part of the git commit message, such as in [1])?
It's true I haven't tested with only a single USB2 phy enabled, but
since the USB design is a derivative from GXL both USB2 PHYs should be
powered on for USB to work.
Pierre-Olivier, can you send a proper revert patch so I can apply it
to fixes and send it asap ?
Thanks for the report !
Neil
>
>
> PS: Neil has probably taken some days off, so please give him more
> than usual time to reply.
>
>
> Best regards,
> Martin
>
>
> [0] https://lore.kernel.org/all/20170814224542.18257-1-martin.blumenstingl@googlemail.com/T/
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=47722220660cfb935e27e62d385959ecc296cddb
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2023-01-02 9:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 22:48 Pierre-Olivier Mercier
2022-12-27 10:43 ` Martin Blumenstingl
2023-01-02 9:50 ` Neil Armstrong [this message]
2023-01-04 14:06 ` [PATCH] Revert "arm64: dts: meson-sm1-odroid-hc4: disable unused USB PHY0" Pierre-Olivier Mercier
2023-01-05 10:29 ` neil.armstrong
2023-01-05 12:02 ` [PATCH v2] " Pierre-Olivier Mercier
2023-01-05 13:57 ` neil.armstrong
2023-01-05 17:15 ` Martin Blumenstingl
2023-01-05 17:52 ` neil.armstrong
2023-01-06 8:13 ` Neil Armstrong
2023-01-06 8:03 ` Neil Armstrong
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=b7dba825-3e39-fbf1-a73f-7e80a0d1bb5c@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=nemunaire@nemunai.re \
/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
all inboxes | Powered by JetHome®