[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1290594227.4446.12.camel@concordia>
Date: Wed, 24 Nov 2010 21:23:47 +1100
From: Michael Ellerman <michael@...erman.id.au>
To: Scott Wood <scottwood@...escale.com>
Cc: Timur Tabi <timur@...escale.com>, Greg KH <gregkh@...e.de>,
Arnd Bergmann <arnd@...db.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Stuart Yoder <stuart.yoder@...escale.com>
Subject: Re: How do I choose an arbitrary minor number for my tty device?
On Thu, 2010-11-18 at 12:13 -0600, Scott Wood wrote:
> On Thu, 18 Nov 2010 11:42:21 -0600
> Timur Tabi <timur@...escale.com> wrote:
>
> > Scott Wood wrote:
> > > We should add a proper bus for the "handles" node. Then sysfs should
> > > show the link between the tty device and a device tree node -- which is
> > > really what we're after, the handle is just a means to that end.
> >
> > How exactly do I do that?
>
> Pass the platform device pointer to tty_register_device.
>
> Then, in the sysfs node, "driver" should be a symlink to
> another sysfs node whose path looks lind of like an OF path.
>
> Unfortunately, it's not an exact match, and the fact that reg doesn't
> translate to a physical address means that AFAICT you'll currently get
> something like "byte-channel.nnn", where "nnn" is an arbitrary
> kernel-assigned number.
Can you not use device_rename() ?
> It would be nice if platform devices that are created from device tree
> nodes included a link to the corresponding /proc/device-tree node in
> their sysfs node.
It's not a link, but the OF path is in devspec, so you can work it out
fairly easily.
cheers
Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)
Powered by blists - more mailing lists