devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David R. Piegdon" <lkml@p23q.org>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
	Alan Stern <stern@rowland.harvard.edu>,
	Chunfeng Yun <chunfeng.yun@mediatek.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Johan Hovold <johan@kernel.org>, Kay Sievers <kay@vrfy.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	Mathias Nyman <mathias.nyman@linux.intel.com>,
	Rob Herring <robh+dt@kernel.org>, Roger Quadros <rogerq@ti.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org, systemd-devel@lists.freedesktop.org
Subject: [RFC PATCH 0/2] USB: DTS: allow suggesting busnumber for platform USB bus via DTS alias
Date: Tue, 27 Nov 2018 16:57:05 +0000	[thread overview]
Message-ID: <20181127165705.GA13460@lagavulin.indurad.x> (raw)

Hi,

on our embedded systems we rely on systemd's persistent netdev names.
Those currently do not work for USB netdevs that are connected to a
platform USB bus.

In https://github.com/systemd/systemd/pull/7273 a systemd patch was
suggested that would allow exactly this, but it was (rightfully) said
that numbering of theses busses is not guaranteed. Internally we used
the patch for a while now, but exactly that has happened with one of our
platforms across different kernel revisions.

The following kernel patches allow suggesting a USB busnumber for each
USB platform bus via a DTS alias, as can be done similarly for many
other devices.
In combination with above systemd patch, these changes allow use of
persistent netdev names also on platform USB busses.

NOTE: this patch might change ordering of busses on devices that use
platform-busses, if aliases for these busses have already been defined!
In the current master there are a few platforms that contain such
aliases, e.g. am33xx, dm814x or imx6qdl

Yours,

David

David R. Piegdon (2):
  usb core: dts: allow suggesting usb bus number for platform busses
  dt-bindings: allow suggesting usb bus number for usb platform busses

 Documentation/devicetree/bindings/usb/usb-hcd.txt |  9 +++++++
 drivers/usb/core/hcd.c                            | 30 ++++++++++++++++++-----
 2 files changed, 33 insertions(+), 6 deletions(-)

-- 
2.11.0

             reply	other threads:[~2018-11-27 16:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27 16:57 David R. Piegdon [this message]
2018-12-11 22:42 ` [RFC PATCH 0/2] USB: DTS: allow suggesting busnumber for platform USB bus via DTS alias Rob Herring

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=20181127165705.GA13460@lagavulin.indurad.x \
    --to=lkml@p23q.org \
    --cc=bigeasy@linutronix.de \
    --cc=chunfeng.yun@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=gustavo@embeddedor.com \
    --cc=johan@kernel.org \
    --cc=kay@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=mathias.nyman@linux.intel.com \
    --cc=robh+dt@kernel.org \
    --cc=rogerq@ti.com \
    --cc=stern@rowland.harvard.edu \
    --cc=systemd-devel@lists.freedesktop.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).