Linux-USB Archive on
 help / color / Atom feed
From: "Bjørn Mork" <>
To: <>
Cc: <>, <>,
	<>, <>,
Subject: Re: [RFC 2/3] ACPI: move ACPI functionality out of r8152 driver
Date: Sat, 24 Aug 2019 12:25:44 +0200
Message-ID: <> (raw)
In-Reply-To: <b84b32cb144f4ba8918ee2406e69275a@AUSX13MPS303.AMER.DELL.COM>

<> writes:

> This change moves ACPI functionality out of the Realtek r8152 driver to
> its own source and header file, making it available to other drivers as
> needed now and into the future.  At the time this ACPI snippet was
> introduced in 2016, only the Realtek driver made use of it in support of
> Dell's enterprise IT policy efforts.  There comes now a need for this
> same support in a different driver, also in support of Dell's enterprise
> IT policy efforts.

Why not make a standalone driver out of this, making the MAC address
(and other system specifc objects?) available to userspace? Then you
can just distribute updated udev rules or systemd units or whatever for
the next docking product.

I don't think system specific policies should be put into device
drivers.  Users will combine systems and devices in ways you don't
foresee, and may have good reasons to want some non-default policy even
for supported combinations.

If you really want to have this policy in the driver(s), then please
consider extending eth_platform_get_mac_address() with an x86/acpi
method.  This will make the device driver code support fetching the mac
address from device tree and Sparc idproms too.  Provided the netdev
folks things this is OK, of course.  This needs to be discussed there,
like would have told you.

Making sure we can modify the MAC address of USB ethernet devices is
obviously a good thing regardless of how/where you fetch it.


  parent reply index

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-23 22:28 Charles.Hyde
2019-08-24  2:41 ` Greg KH
2019-08-24 10:25 ` Bjørn Mork [this message]
2019-08-24 13:24   ` Mario.Limonciello
2019-08-27 22:08     ` Charles.Hyde
2019-08-27 22:19       ` Mario.Limonciello
2019-08-28 16:41         ` Charles.Hyde

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-USB Archive on

Archives are clonable:
	git clone --mirror linux-usb/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-usb linux-usb/ \
	public-inbox-index linux-usb

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox