linux-kernel - Re: [spi-devel-general] [PATCH 3/4] spi: Add OF binding support for SPI busses

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 24 May 2008 00:13:27 -0700
From:	David Brownell <david-b@...bell.net>
To:	"Grant Likely" <grant.likely@...retlab.ca>
Cc:	spi-devel-general@...ts.sourceforge.net,
	"Segher Boessenkool" <segher@...nel.crashing.org>,
	linux-kernel@...r.kernel.org, linuxppc-dev@...abs.org,
	fabrizio.garetto@...il.com,
	"Guennadi Liakhovetski" <g.liakhovetski@....de>
Subject: Re: [spi-devel-general] [PATCH 3/4] spi: Add OF binding support for SPI busses

On Friday 23 May 2008, Grant Likely wrote:
> Very good point.  Okay, so we cannot assume any correlation between
> the number of CS lines and the number of child nodes to the SPI bus.

That wasn't what I was implying ... all the devices hooked
up to a given chipselect should be viewed as a single (albeit
composite) child node.

Now, the driver for that child node may want to expose lots
of substructure.  But that's no different from any other
complex device, whose protocol happens to embed some notion
of component addressing.

It's just that in the case I mentioned, that addressing is
a bit more externally visible than it is in some other cases.

- Dave

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/