linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: [PATCH 0/2] Add some uevent variables on DVB to support persistent names on udev
Date: Tue, 20 Feb 2024 10:46:00 +0100	[thread overview]
Message-ID: <cover.1708422122.git.mchehab@kernel.org> (raw)

As pointed by https://github.com/systemd/systemd/issues/31406,
currently, udev doesn't have pesistent names for the subsystem.

Add adapter's name and device's parent device, as those may help
adding unique persistent names.

While here, also change em28xx-dvb to use a real name instead of
the parent dev name. With that,  uevent for DVB devnodes will
resemble this:

/sys/class/dvb/dvb0.demux0/uevent:MAJOR=212
/sys/class/dvb/dvb0.demux0/uevent:MINOR=1
/sys/class/dvb/dvb0.demux0/uevent:DEVNAME=dvb/adapter0/demux0
/sys/class/dvb/dvb0.demux0/uevent:DVB_ADAPTER_NAME=PCTV nanoStick T2 290e
/sys/class/dvb/dvb0.demux0/uevent:DVB_ADAPTER_PDEV=2-1:1.0
/sys/class/dvb/dvb0.demux0/uevent:DVB_ADAPTER_NUM=0
/sys/class/dvb/dvb0.demux0/uevent:DVB_DEVICE_TYPE=demux
/sys/class/dvb/dvb0.demux0/uevent:DVB_DEVICE_NUM=0

Tested with a PCTV nanoStick T2 290e device.

Mauro Carvalho Chehab (2):
  media: dvbdev: export adapter's name and bus ID to DVB uevent
    variables
  em28xx-dvb: fix DVB adapter device name

 drivers/media/dvb-core/dvbdev.c       | 2 ++
 drivers/media/usb/em28xx/em28xx-dvb.c | 2 +-
 2 files changed, 3 insertions(+), 1 deletion(-)

-- 
2.43.0



             reply	other threads:[~2024-02-20  9:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20  9:46 Mauro Carvalho Chehab [this message]
2024-02-20  9:46 ` [PATCH 1/2] media: dvbdev: export adapter's name and bus ID to DVB uevent variables Mauro Carvalho Chehab
2024-02-26  8:41   ` Hans Verkuil
2024-02-20  9:46 ` [PATCH 2/2] em28xx-dvb: fix DVB adapter device name Mauro Carvalho Chehab
2024-02-26  9:03   ` Hans Verkuil

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=cover.1708422122.git.mchehab@kernel.org \
    --to=mchehab@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@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;
as well as URLs for NNTP newsgroup(s).