From: Ernst Schwab <eschwab-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [PATCH] of: add bus-number specification to spi_mpc8xxx
Date: Tue, 16 Feb 2010 19:59:43 +0100 [thread overview]
Message-ID: <20100216195943.e40e104e.eschwab@online.de> (raw)
In-Reply-To: <fa686aa41002160718u36fe6f7ey7be83ab69317ec76-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org> wrote:
> Add a property to the /chosen node to assign short labels to devices.
I'm not familiar with this and will check - does anyone know of an
existing example for this?
> Unless you're trying to line up disparate data structure, the actually
> number assigned to a bus really doesn't matter. It is better to let
> Linux dynamically assign than to manually maintain the assigned bus
> numbers for each machine. Assuming dynamic assignment also protects
> against breaking userspace applications when, for whatever reason, the
> bus numbers get shuffled on a platform.
Hm. What if we have two identical devices, lets say EEPROMs at25,
connected to two SPI controllers. These are set up as
/sys/bus/spi/devices/spi32766.0/eeprom and
/sys/bus/spi/devices/spi32765.0/eeprom.
How can userspace code determine which one it should
use if it needs to use the one connected to the first spi controller?
Can this be solved with the /chosen mechanism?
Regards
Ernst
------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
next prev parent reply other threads:[~2010-02-16 18:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 14:08 [PATCH] of: add bus-number specification to spi_mpc8xxx Ernst Schwab
[not found] ` <20100216150850.d966cd79.eschwab-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org>
2010-02-16 14:28 ` Grant Likely
[not found] ` <fa686aa41002160628g62bd6564h50e712e8fb9c384d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-16 15:08 ` Ernst Schwab
[not found] ` <20100216160832.730cb00b.eschwab-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org>
2010-02-16 15:18 ` Grant Likely
[not found] ` <fa686aa41002160718u36fe6f7ey7be83ab69317ec76-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-16 18:59 ` Ernst Schwab [this message]
[not found] ` <20100216195943.e40e104e.eschwab-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org>
2010-02-16 21:23 ` Grant Likely
[not found] ` <fa686aa41002161323v72dbcdb4rd28ece040c878972-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-17 11:11 ` Ernst Schwab
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=20100216195943.e40e104e.eschwab@online.de \
--to=eschwab-bgeptl67xyczqb+pc5nmwq@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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