From: Prashant Malani <pmalani@chromium.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Benson Leung <bleung@chromium.org>
Subject: Re: [PATCH] usb: typec: pd: Add symlink to linked device
Date: Mon, 21 Nov 2022 07:16:03 +0000 [thread overview]
Message-ID: <Y3sls9+NcQrdjb9y@chromium.org> (raw)
In-Reply-To: <Y3scND+8DVe8SGeD@kroah.com>
Hi Greg,
Thanks for reviewing the patch.
On Nov 21 07:35, Greg Kroah-Hartman wrote:
> On Mon, Nov 21, 2022 at 06:20:39AM +0000, Prashant Malani wrote:
> >
> > +What: /sys/class/usb_power_delivery/.../device
> > +Date: November 2022
> > +Contact: Prashant Malani <pmalani@chromium.org>
> > +Description:
> > + Symbolic link to the directory of the device to which the USB PD object is linked.
>
> Line is way too long.
Sorry about that. I'll try to make it more concise in the next version.
>
> But wait, a "device" has a specific meaning in a sysfs file, and that is
> not what is happening here.
>
> Please don't make fake "device" symlinks when these are not really using
> a device here. Either fix it up to properly use the device structures
> in the code, or call this something else.
Got it, sorry about using that specific term. How about:
1. "linked_device"
2. "base_device" ?
I prefer 1.) but happy to use the other, or any other suggestion.
>
> What in userspace wants to see this symlink?
ChromeOS's userspace Type-C daemon. It listens for Type-C partner uevents, but the PD objects
can be created later (and destroyed and then recreated again, for PD chargers which dynamically
change their source caps), and this helps determine which partner does those events apply to.
Thanks,
-Prashant
next prev parent reply other threads:[~2022-11-21 7:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 6:20 [PATCH] usb: typec: pd: Add symlink to linked device Prashant Malani
2022-11-21 6:35 ` Greg Kroah-Hartman
2022-11-21 7:16 ` Prashant Malani [this message]
2022-11-21 7:36 ` Greg Kroah-Hartman
2022-11-21 19:11 ` Prashant Malani
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=Y3sls9+NcQrdjb9y@chromium.org \
--to=pmalani@chromium.org \
--cc=bleung@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.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