linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Tony Lindgren <tony@atomide.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Jiri Slaby" <jirislaby@kernel.org>,
	"Dhruva Gole" <d-gole@ti.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"John Ogness" <john.ogness@linutronix.de>,
	"Johan Hovold" <johan@kernel.org>,
	"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	linux-omap@vger.kernel.org, linux-serial@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial: core: Add sysfs links for serial core port instances for ttys
Date: Wed, 19 Jul 2023 08:33:44 +0300	[thread overview]
Message-ID: <ZLd1uCKoGMBruwiN@smile.fi.intel.com> (raw)
In-Reply-To: <20230719051613.46569-1-tony@atomide.com>

On Wed, Jul 19, 2023 at 08:16:11AM +0300, Tony Lindgren wrote:
> Let's allow the userspace to find out the tty name for a serial core
> controller id if a tty exists. This can be done with:
> 
> $ grep DEVNAME /sys/bus/serial-base/devices/port*/tty/uevent
> /sys/bus/serial-base/devices/port.00:04.0/tty/uevent:DEVNAME=ttyS0
> /sys/bus/serial-base/devices/port.serial8250.1/tty/uevent:DEVNAME=ttyS1
> /sys/bus/serial-base/devices/port.serial8250.2/tty/uevent:DEVNAME=ttyS2
> /sys/bus/serial-base/devices/port.serial8250.3/tty/uevent:DEVNAME=ttyS3

What part is the controller ID here?

We also have something in procfs (I don't remember what info exactly is there).

> And with this, we can add /dev/serial/by-id symlinks to the serial port
> device instances so we can start using serial core port addressing in
> addition to the legacy ttyS naming.
> 
> The naming we can use is dev_name:0.0 where 0.0 are the serial core
> controller id and port id, so for the ttyS0 example above the naming
> would be 00:04.0:0.0.

This is interesting idea. But any hint why it can be useful?

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2023-07-19  5:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-19  5:16 [PATCH] serial: core: Add sysfs links for serial core port instances for ttys Tony Lindgren
2023-07-19  5:33 ` Andy Shevchenko [this message]
2023-07-19  5:43   ` Tony Lindgren
2023-07-19 13:59     ` Andy Shevchenko
2023-07-20  4:13       ` Tony Lindgren
2023-07-21 10:05         ` Andy Shevchenko
2023-07-24  5:26           ` 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=ZLd1uCKoGMBruwiN@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=bigeasy@linutronix.de \
    --cc=d-gole@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jirislaby@kernel.org \
    --cc=johan@kernel.org \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=tony@atomide.com \
    --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 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).