From: Sicelo <absicsz@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
maemo-leste@lists.dyne.org, Felipe Balbi <balbi@kernel.org>,
phone-devel@vger.kernel.org, Bin Liu <b-liu@ti.com>,
Rob Herring <robh@kernel.org>,
"H. Nikolaus Schaller" <hns@goldelico.com>
Subject: Re: USB PHY Initialization Fails on Nokia N900 Since 5.19
Date: Fri, 18 Nov 2022 11:24:48 +0200 [thread overview]
Message-ID: <Y3dPYEaqVfXFmyYf@tp440p.steeds.sam> (raw)
In-Reply-To: <Y3c+VSLcH+c2sLGr@atomide.com>
> OK thanks that helps, I think it's because the platform IRQ resources are
> no longer being automatically populated from devicetree because of the
> issues with deferred probe.
>
> Maybe give the following patch a try and see if it helps?
>
> Then assuming this works as a fix I'll post further changes to make also
> omap2430 glue layer to probe with ti-sysc interconnect target module
> driver in call cases.
Hi Tony
Thank you very much. This patch works well on the N900.
`cat /sys/firmware/devicetree/base/ocp@68000000/usb_otg_hs@480ab000/interrupts`
still returns null, but from your explanation, I guess this is expected.
In case this gets published in its current form, you're free to add:
Tested-By: Sicelo Mhlongo <absicsz@gmail.com>
prev parent reply other threads:[~2022-11-18 9:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 9:08 USB PHY Initialization Fails on Nokia N900 Since 5.19 Sicelo
2022-10-11 5:39 ` [maemo-leste] " Tony Lindgren
2022-10-11 10:44 ` Sicelo
2022-11-11 8:36 ` Sicelo
2022-11-18 8:12 ` Tony Lindgren
2022-11-18 9:24 ` Sicelo [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=Y3dPYEaqVfXFmyYf@tp440p.steeds.sam \
--to=absicsz@gmail.com \
--cc=b-liu@ti.com \
--cc=balbi@kernel.org \
--cc=hns@goldelico.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=maemo-leste@lists.dyne.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tony@atomide.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).