From: Tony Lindgren <tony@atomide.com>
To: Romain Naour <romain.naour@smile.fr>
Cc: 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 09:40:49 +0300 [thread overview]
Message-ID: <YzKa8csiFaJik79O@atomide.com> (raw)
In-Reply-To: <edf56bca-3f90-5cac-7c21-085f4a563dac@smile.fr>
Hi,
* Romain Naour <romain.naour@smile.fr> [220921 08:13]:
> Ok, I understand what's going on...
>
> The issue appear on the merge commit since on a omap side there was the switch
> to ti-sysc (devicetree interconnect description) and on upstream side there was
> a change on driver core behavior with fw_devlink=on being set by default:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ea718c699055c8566eb64432388a04974c43b2ea
OK good to hear it's not the change to ti-sysc. That should be all pretty
much standard Linux driver related changes.
> Actually the issue is really on the TI's prueth and IEP driver whith
> fw_devlink=on. The IEP driver probe correctly with fw_devlink=permissive.
Argh not again, the fw_devlink changes seem to be causing all kind of
issues. Any ideas what the issue here might be? It might be worth testing
with v6.0-rc7 too as it has a series of fixes to related issues.
Regards,
Tony
next prev parent reply other threads:[~2022-09-27 6:40 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 [this message]
2022-09-27 8:04 ` Vignesh Raghavendra
2022-09-27 10:11 ` Romain Naour
2022-09-27 10:30 ` Tony Lindgren
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=YzKa8csiFaJik79O@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 \
/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.