All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Greg KH <greg@kroah.com>
Cc: Dave Boutcher <sleddog@us.ibm.com>, Ryan Arnold <rsa@us.ibm.com>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	boutcher@us.ibm.com, Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: new driver (hvcs) review request and sysfs questions
Date: Wed, 25 Feb 2004 22:34:34 +1100	[thread overview]
Message-ID: <1077708874.22213.13.camel@gaston> (raw)
In-Reply-To: <20040225042224.GA5135@kroah.com>

On Wed, 2004-02-25 at 15:22, Greg KH wrote:
> On Tue, Feb 24, 2004 at 09:12:09PM -0600, Dave Boutcher wrote:
> > 
> > It is also true that it is unlike the representation of most other things 
> > in sysfs, so perhaps this is the time to change before it gets too baked 
> > into things.
> 
> I agree.  Is there any reason we _have_ to stick with the OF names?  It
> seems to me to make more sense here not to, to make it more like the
> rest of the kernel.
> 
> That is, if the address after the @ is unique.  Is that always the case?

That is the problem... I didn't check my OF spec, but I do remember
clearly cases where the "unit address" isn't unique... This happens
typically at the root of the device-tree, or with pseudo devices,
where you can have several entries with an @0 unit address. However,
I yet have to see that for things that are worth putting into sysfs ;)

One thing though is that it's only unique at a given level of
hierarchy. The Unit Address in OF has no meaning outside of the
context of the parent bus. That may be just fine for sysfs, but
if I take as an example the PCI devices, they do have a globally
unique ID here with the domain number.

Ben.



  reply	other threads:[~2004-02-25 11:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-25  0:00 new driver (hvcs) review request and sysfs questions Ryan Arnold
2004-02-25  1:28 ` Greg KH
2004-02-25  3:12   ` Dave Boutcher
2004-02-25  4:22     ` Greg KH
2004-02-25 11:34       ` Benjamin Herrenschmidt [this message]
2004-02-25 15:46         ` device/kobject naming Hollis Blanchard
2004-02-26  0:18           ` Greg KH
2004-02-26 21:31             ` Hollis Blanchard
2004-02-25 16:22 ` new driver (hvcs) review request and sysfs questions Dave Hansen

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=1077708874.22213.13.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=boutcher@us.ibm.com \
    --cc=greg@kroah.com \
    --cc=hollisb@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rsa@us.ibm.com \
    --cc=sleddog@us.ibm.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.