From: Timur Tabi <timur@freescale.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, sr@denx.de
Subject: Re: [PATCH] powerpc: add of_find_next_property and of_get_aliased_index
Date: Wed, 25 Jun 2008 15:27:05 -0500 [thread overview]
Message-ID: <4862AA19.3030502@freescale.com> (raw)
In-Reply-To: <762468c24d365ca8397b5833aa172b95@kernel.crashing.org>
Segher Boessenkool wrote:
> It returns 2 for both "i2c-1" and "i2c-2".
Well, I'm assuming that the alias property names will follow the current
convention of xxxxnn where xxxx is a name and nn is a number. No dashes or
other punctuation.
> Also, alias names do not have any significance in general, they are
> just handy shortcut names for humans to use; it would be better not
> to overload this. What do you want to use this for?
As an alternative to cell-index or device-id for enumerating devices. The
consensus from the '"cell-index" vs. "index" vs. no index in I2C device nodes'
thread is that aliases are to be used to enumerate devices.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-06-25 20:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 20:05 [PATCH] powerpc: add of_find_next_property and of_get_aliased_index Timur Tabi
2008-06-25 20:22 ` Segher Boessenkool
2008-06-25 20:27 ` Timur Tabi [this message]
2008-06-25 23:35 ` Segher Boessenkool
2008-06-26 15:12 ` Timur Tabi
2008-06-26 15:51 ` Stefan Roese
2008-06-26 15:55 ` Timur Tabi
2008-06-26 18:27 ` [PATCH] powerpc: add of_find_next_property andof_get_aliased_index Sean MacLennan
2008-06-26 18:29 ` Timur Tabi
2008-06-26 18:41 ` Stefan Roese
2008-06-27 1:30 ` David Gibson
2008-07-03 13:33 ` Josh Boyer
2008-07-03 13:43 ` Stefan Roese
2008-06-25 23:51 ` [PATCH] powerpc: add of_find_next_property and of_get_aliased_index Josh Boyer
2008-06-26 10:57 ` Benjamin Herrenschmidt
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=4862AA19.3030502@freescale.com \
--to=timur@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=segher@kernel.crashing.org \
--cc=sr@denx.de \
/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.