From: Tony Lindgren <tony@atomide.com>
To: Romain Naour <romain.naour@smile.fr>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Linux-OMAP <linux-omap@vger.kernel.org>,
"rogerq@kernel.org >> Roger Quadros" <rogerq@kernel.org>,
Md Danish Anwar <danishanwar@ti.com>
Subject: Re: prueth: IEP driver doesn't probe anymore
Date: Tue, 27 Sep 2022 13:30:38 +0300 [thread overview]
Message-ID: <YzLQzok4Wo9hHBop@atomide.com> (raw)
In-Reply-To: <276295a7-c6e0-5200-f6da-9c7298c914be@smile.fr>
* Romain Naour <romain.naour@smile.fr> [220927 10:03]:
> I rebased the prueth + IEP series on v6.0-rc7 and indeed the driver probe
> correctly but with some delay due deferred probe.
OK great. FYI, see commit 0b3acd1cc022 ("Merge tag 'driver-core-6.0-rc4' of
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core") for details
on what got merged.
> [ 9.568817] remoteproc remoteproc0: 4b234000.pru is available
> [ 9.580505] remoteproc remoteproc1: 4b238000.pru is available
> [ 9.625701] remoteproc remoteproc2: 4b2b4000.pru is available
> [ 9.632110] remoteproc remoteproc3: 4b2b8000.pru is available
> [ 9.932952] prueth pruss1_eth: unable to get IEP
> [ 10.238098] prueth pruss1_eth: unable to get IEP
> [ 10.469421] prueth pruss1_eth: unable to get IEP
> [ 10.675445] prueth pruss1_eth: unable to get IEP
> [ 10.885589] prueth pruss1_eth: unable to get IEP
> [ 11.117126] prueth pruss1_eth: unable to get IEP
> [ 11.755462] prueth pruss1_eth: unable to get IEP
> [ 12.316192] prueth pruss1_eth: unable to get IEP
> [ 13.387969] prueth pruss1_eth: unable to get IEP
> [ 14.175750] prueth pruss1_eth: unable to get IEP
> [ 14.388671] prueth pruss1_eth: unable to get IEP
> [ 14.648406] prueth pruss1_eth: unable to get IEP
> [ 16.946716] prueth pruss1_eth: unable to get IEP
> [ 25.037414] remoteproc remoteproc1: powering up 4b238000.pru
> [ 25.056793] remoteproc remoteproc1: Booting fw image
> ti-pruss/am57xx-pru1-prueth-fw.elf, size 6952
> [ 25.065856] remoteproc remoteproc1: unsupported resource 5
> [ 25.071472] remoteproc remoteproc1: remote processor 4b238000.pru is now up
> [ 25.157104] remoteproc remoteproc0: powering up 4b234000.pru
> [ 25.165527] remoteproc remoteproc0: Booting fw image
> ti-pruss/am57xx-pru0-prueth-fw.elf, size 6920
> [ 25.174713] remoteproc remoteproc0: unsupported resource 5
> [ 25.180328] remoteproc remoteproc0: remote processor 4b234000.pru is now up
> [ 27.047607] prueth pruss1_eth eth4: Link is Up - 100Mbps/Full - flow control off
Seem like this is still not ideal with delayed and noisy deferred probe :(
Regards,
Tony
prev parent reply other threads:[~2022-09-27 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 8:55 prueth: IEP driver doesn't probe anymore Romain Naour
2022-09-19 8:07 ` Romain Naour
2022-09-21 8:21 ` Romain Naour
2022-09-27 6:40 ` Tony Lindgren
2022-09-27 8:04 ` Vignesh Raghavendra
2022-09-27 10:11 ` Romain Naour
2022-09-27 10:30 ` 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=YzLQzok4Wo9hHBop@atomide.com \
--to=tony@atomide.com \
--cc=danishanwar@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=rogerq@kernel.org \
--cc=romain.naour@smile.fr \
--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 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.