dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Clark <robdclark@gmail.com>
To: Dave Airlie <airlied@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [RFC] drm platform multi-device support
Date: Mon, 4 Apr 2011 22:08:29 -0500	[thread overview]
Message-ID: <BANLkTimh4MVvDFfLP-go4A04kV17_ZtjCw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=cjGWaQep=ypO0BqrDGU9Jzd_5jA@mail.gmail.com>

On Mon, Apr 4, 2011 at 7:30 PM, Dave Airlie <airlied@gmail.com> wrote:
> On Wed, Mar 30, 2011 at 2:44 AM, Rob Clark <rob@ti.com> wrote:
>> From: Rob Clark <robdclark@gmail.com>
>>
>> Include the minor device id in the bus-id to give userspace a way to open
>> the correct "cardN" when there are multiple device instances.
>> ---
>> It may seem a bit strange to have multiple platform device instances, but
>> we have a use-case for this.  And this relatively simple patch does the
>> trick.
>
> I'm finding it hard to like this since I feel it might limit certain
> thing in the future, by baking
> this into the ABI.
>
> We have plans for multiple device nodes per device, but they don't
> involve abusing the bus id like this.
>
> Surely you'd just have another platform device with another unique
> name for this, I'd be more willing
> to accept some sort of unique id stored in the platformdev or drm that
> isn't the device node.

What about:

		len = snprintf(master->unique, master->unique_len,
			"platform:%s:%02d", dev->platformdev->name, dev->platformdev->id);

(ie. using the id field from struct platform_device)..

Perhaps this is more analogous to using pci bus # / slot / func?

BR,
-R

  reply	other threads:[~2011-04-05  3:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29 16:44 [RFC] drm platform multi-device support Rob Clark
2011-03-30 12:57 ` Ilija Hadzic
2011-03-30 14:26   ` Rob Clark
2011-04-05  0:30 ` Dave Airlie
2011-04-05  3:08   ` Rob Clark [this message]
2011-04-06  1:21     ` Dave Airlie
2011-07-14  3:12 ` [PATCH] drm: " Rob Clark

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=BANLkTimh4MVvDFfLP-go4A04kV17_ZtjCw@mail.gmail.com \
    --to=robdclark@gmail.com \
    --cc=airlied@gmail.com \
    --cc=dri-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