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: [maemo-leste] USB PHY Initialization Fails on Nokia N900 Since 5.19
Date: Tue, 11 Oct 2022 12:44:11 +0200 [thread overview]
Message-ID: <Y0VI+/XJs8nsazwE@tp440p.steeds.sam> (raw)
In-Reply-To: <Y0UBindrJa1ptyR0@atomide.com>
On Tue, Oct 11, 2022 at 08:39:22AM +0300, Tony Lindgren wrote:
> To me it seems that we now somehow have a probe issue for musb depending
> on how it gets probed depending on the following line:
>
> device_set_of_node_from_dev(&musb->dev, &pdev->dev);
>
> I think commit 239071064732 ("partially Revert "usb: musb: Set the DT node
> on the child device"") fixed the issue for omap3 that still uses hwmod
> by removing the device_set_of_node_from_dev(). However, it somehow broke
> SoCs using ti-sysc like omap4.
>
> My guess is commit 239071064732 will fix the issue for you?
Hi Tony
Thanks for the suggestion. However, 239071064732 does not fix it for me.
With that in place, there is no trace created automatically, but dmesg
shows:
[ 1.389648] musb-hdrc musb-hdrc.0.auto: error -ENXIO: IRQ mc not found
I wonder if there is something to update on the N900 dts perhaps, in
connection with the recent musb changes?
Regards
next prev parent reply other threads:[~2022-10-11 10:44 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 [this message]
2022-11-11 8:36 ` Sicelo
2022-11-18 8:12 ` Tony Lindgren
2022-11-18 9:24 ` Sicelo
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=Y0VI+/XJs8nsazwE@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.