From: Daniel Vetter <daniel@ffwll.ch>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: devicetree@vger.kernel.org,
Maxime Ripard <maxime.ripard@bootlin.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
David Airlie <airlied@linux.ie>, Rob Herring <robh+dt@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sean Paul <sean@poorly.run>
Subject: Re: [PATCH] drm: support gpu aliases defined in DT data
Date: Thu, 17 Jan 2019 14:26:04 +0100 [thread overview]
Message-ID: <CAKMK7uEUhPtmyujMGb-YNbrhYM9tqVc2S+=cJFWQvQOeSRaSnw@mail.gmail.com> (raw)
In-Reply-To: <a96c03af-4a01-4c85-f8ab-9e4d52822cf1@ti.com>
On Thu, Jan 17, 2019 at 2:04 PM Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
>
> On 17/01/19 14:33, Daniel Vetter wrote:
> > On Thu, Jan 17, 2019 at 01:19:18PM +0200, Tomi Valkeinen wrote:
> >> The DRM device minor numbers are allocated according to the registration
> >> order. This causes confusion in cases where the registration order can
> >> change, or when, say, a modesetting capable device is preferred to be
> >> card0, and a rendering device is preferred to be card1.
> >>
> >> This patch adds similar functionality that is used in some other
> >> subsystems, where device minor numbers can be defined in DT bindings'
> >> aliases node.
> >
> > What other subsystem? I thought that minor numbers shouldn't be made uapi,
> > and that udev or similar is supposed to give you stable names ... Is that
> > not the case on SoC?
>
> I think at least i2c, spi and uart use DT aliases.
Commits/code implementing would be best.
> I also have my doubts about this, but thought to post this to get some
> comments, as it does make life quite a bit easier =).
Yeah I think "soc without udev" seems reasonable assumption, I just
think this is something the overall soc community should agree on as a
good thing to do. I guess since the of stuff you're using is generic
that's all happened already, so should amount to gathering a pile of
acks and then merging it.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-01-17 13:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 11:19 [PATCH] drm: support gpu aliases defined in DT data Tomi Valkeinen
2019-01-17 11:35 ` Maxime Ripard
2019-01-17 12:33 ` Daniel Vetter
2019-01-17 13:04 ` Tomi Valkeinen
2019-01-17 13:26 ` Daniel Vetter [this message]
2019-01-17 13:56 ` Tomi Valkeinen
2019-01-17 22:04 ` Rob Herring
2019-01-18 8:29 ` Tomi Valkeinen
2019-03-06 1:41 ` Laurent Pinchart
2019-03-06 7:49 ` Tomi Valkeinen
2019-04-17 17:42 ` Emil Velikov
2019-04-26 11:23 ` Tomi Valkeinen
2019-01-17 21:38 ` Eric Anholt
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='CAKMK7uEUhPtmyujMGb-YNbrhYM9tqVc2S+=cJFWQvQOeSRaSnw@mail.gmail.com' \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=maxime.ripard@bootlin.com \
--cc=robh+dt@kernel.org \
--cc=sean@poorly.run \
--cc=tomi.valkeinen@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).