All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: Greg KH <greg@kroah.com>
Cc: Jonathan Cameron <jic23@cam.ac.uk>,
	LKML <linux-kernel@vger.kernel.org>,
	Manuel Stahl <manuel.stahl@iis.fraunhofer.de>,
	"Hennerich, Michael" <Michael.Hennerich@analog.com>,
	"Frysinger, Michael" <Michael.Frysinger@analog.com>,
	"Getz, Robin" <Robin.Getz@analog.com>,
	Jean Delvare <khali@linux-fr.org>,
	"Trisal, Kalhan" <kalhan.trisal@intel.com>,
	"Zhang, Xing Z" <xing.z.zhang@intel.com>,
	Ira Snyder <iws@ovro.caltech.edu>
Subject: Re: [RFC] Staging:IIO: New ABI
Date: Wed, 20 Jan 2010 17:40:06 +0100	[thread overview]
Message-ID: <ac3eb2511001200840v185617ecm60b5282cb810a4fb@mail.gmail.com> (raw)
In-Reply-To: <20100120153748.GA29401@kroah.com>

On Wed, Jan 20, 2010 at 16:37, Greg KH <greg@kroah.com> wrote:
> On Wed, Jan 20, 2010 at 03:13:40PM +0000, Jonathan Cameron wrote:
>> What:        /sys/class/iio/ring_buffer[m]
>> Description:
>>               Link to /sys/class/iio/device[n]/ring_buffer[m]. Ring buffer
>>               numbering may not match that of device as some devices do not
>>               have ring buffers.
>
> Why is this link needed?  Why can't you just look in the device
> directory for a ring buffer?  And wouldn't the ring buffer be 1..n for
> every device?  They shouldn't be "unique" for all iio devices, that
> would be wierd.

I think with the hidden class kobject we successfully prevent any
custom links from being created there. :) The class sysfs layout does
not allow custom links added to its single directory, it confuses
userspace.

Jonathan, if you need anything like this, please consider using a
"bus_type", which has the proper userspace interface. The "class"
interface can not be extended to make such things possible.

Thanks,
Kay

  reply	other threads:[~2010-01-20 16:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-20 15:13 [RFC] Staging:IIO: New ABI Jonathan Cameron
2010-01-20 15:37 ` Greg KH
2010-01-20 16:40   ` Kay Sievers [this message]
2010-01-20 16:53   ` Jonathan Cameron
2010-01-20 17:14     ` Kay Sievers
2010-01-25 18:52       ` Jonathan Cameron
2010-01-22 20:47     ` Greg KH
2010-01-23  0:14       ` Dmitry Torokhov
2010-01-23  0:31         ` Greg KH
2010-01-26  9:34           ` Dmitry Torokhov
2010-01-26  9:55             ` Hennerich, Michael
2010-01-26 10:11               ` Dmitry Torokhov
2010-01-26 10:25                 ` Hennerich, Michael
2010-01-26 10:33                   ` Manuel Stahl
2010-01-26 11:10                   ` Jonathan Cameron
2010-01-27  7:07             ` Pavel Machek
2010-01-24 11:27       ` Jonathan Cameron

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=ac3eb2511001200840v185617ecm60b5282cb810a4fb@mail.gmail.com \
    --to=kay.sievers@vrfy.org \
    --cc=Michael.Frysinger@analog.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=Robin.Getz@analog.com \
    --cc=greg@kroah.com \
    --cc=iws@ovro.caltech.edu \
    --cc=jic23@cam.ac.uk \
    --cc=kalhan.trisal@intel.com \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manuel.stahl@iis.fraunhofer.de \
    --cc=xing.z.zhang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.