From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Saravana Kannan <saravanak@google.com>
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Stephen Boyd <sboyd@kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH] Revert "of: property: fw_devlink: Add support for remote-endpoint"
Date: Tue, 28 Sep 2021 14:30:47 +0200 [thread overview]
Message-ID: <YVMK90kRtkBxptlR@kroah.com> (raw)
In-Reply-To: <CAGETcx_HRmvDKuXQEJkMk7zBpedLGkQmvJ24tAWpCHFf4DPX_w@mail.gmail.com>
On Mon, Sep 27, 2021 at 06:13:12PM -0700, Saravana Kannan wrote:
> On Mon, Sep 27, 2021 at 5:56 PM Dmitry Baryshkov
> > root@qcom-armv8a:~# ls -l /sys/bus/platform/devices/88e9000.phy/
> > lrwxrwxrwx 1 root root 0 Aug 4 15:13
> > consumer:platform:a600000.usb ->
> > ../../../virtual/devlink/platform:88e9000.phy--platform:a600000.usb
> > lrwxrwxrwx 1 root root 0 Aug 4 15:13
> > consumer:platform:af00000.clock-controller ->
> > ../../../virtual/devlink/platform:88e9000.phy--platform:af00000.clock-controller
> > -rw-r--r-- 1 root root 4096 Aug 4 15:13 driver_override
> > -r--r--r-- 1 root root 4096 Aug 4 15:13 modalias
> > lrwxrwxrwx 1 root root 0 Aug 4 15:13 of_node ->
> > ../../../../firmware/devicetree/base/soc@0/phy@88e9000
> > drwxr-xr-x 2 root root 0 Aug 4 15:13 power
> > lrwxrwxrwx 1 root root 0 Aug 4 15:10 subsystem ->
> > ../../../../bus/platform
> > lrwxrwxrwx 1 root root 0 Aug 4 15:13
> > supplier:platform:100000.clock-controller ->
> > ../../../virtual/devlink/platform:100000.clock-controller--platform:88e9000.phy
> > lrwxrwxrwx 1 root root 0 Aug 4 15:13
> > supplier:platform:18200000.rsc:clock-controller ->
> > ../../../virtual/devlink/platform:18200000.rsc:clock-controller--platform:88e9000.phy
> > lrwxrwxrwx 1 root root 0 Aug 4 15:13
> > supplier:platform:18200000.rsc:pm8150-rpmh-regulators ->
> > ../../../virtual/devlink/platform:18200000.rsc:pm8150-rpmh-regulators--platform:88e9000.phy
> > -rw-r--r-- 1 root root 4096 Aug 4 15:10 uevent
> > -r--r--r-- 1 root root 4096 Aug 4 15:13
> > waiting_for_supplier
> >
> > Thus it is not possible to spot this device link without
> > CONFIG_DEBUG_DRIVER=y (or any similar debugging technique).
>
> I sent out some patches to make this easier. But doesn't look like
> it'll land in 5.15.
> https://lore.kernel.org/lkml/20210915172808.620546-1-saravanak@google.com/
I have now queued these up to make it into 5.15-final, this thread has
convinced me :)
greg k-h
next prev parent reply other threads:[~2021-09-28 12:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210927204830.4018624-1-dmitry.baryshkov@linaro.org>
[not found] ` <CAGETcx-3Y3rOSoXu3SbDa6BP_jcT8uSQA+MV55QCY4b0Oe7L-A@mail.gmail.com>
2021-09-28 0:56 ` [PATCH] Revert "of: property: fw_devlink: Add support for remote-endpoint" Dmitry Baryshkov
2021-09-28 1:13 ` Saravana Kannan
2021-09-28 12:30 ` Greg Kroah-Hartman [this message]
2021-09-28 16:37 ` Saravana Kannan
2021-10-02 1:04 ` Dmitry Baryshkov
2021-10-02 1:21 ` Saravana Kannan
2021-10-06 0:21 ` Saravana Kannan
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=YVMK90kRtkBxptlR@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=frowand.list@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=saravanak@google.com \
--cc=sboyd@kernel.org \
/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).