Grant, Anton,
[snip]
Doing this in parallel will speed things up significantly.
Yeah; Then I would handle it as a separate cs# and map it to enabling
multiple CS lines at a time.
sounds reasonable - will do it that way.
BTW: would drivers/misc be a proper location ?
Who's
IRQs are already disabled here so we don't need to disable them again.
But more importantly, the spin_lock_irqsave() overwrites flags and
that breaks things when we want to re-enable the IRQs when we call
spin_unlock_irqrestore(ha-hardware_lock, flags);
Signed-off-by: Dan Carpenter
On Thu, Sep 09, 2010 at 09:07:59AM +0800, Jeremy Kerr wrote:
Hi Nicolas,
What Jeremy did is to add a probe_dt method in the mdesc structure, and
then the core is calling them in sequence until one of them returns
success.
now, the compatible property is explained here:
On Sun, Sep 12, 2010 at 05:10:35PM +0200, André Schwarz wrote:
BTW: would drivers/misc be a proper location ?
Who's supposed to pick that driver up and on what list shall I post it
for review ?
You should cc spi-devel-general, and feel free to cc me. drivers/misc
would probably be
Hi Linus,
Here's a double handfull of SPI and OF (ll_temac, gpiolib, 52xx_uart).
Should be nothing eyebrow raising here.
g.
The following changes since commit be6200aac985e0a3db56ec636763a32f3e32e7f1:
Linus Torvalds (1):
Merge branch 'kvm-updates/2.6.36' of
Hi David,
Hrm. The trouble with this idea is that it needs some measure of
specificness of match,
I was originally thinking an enum, something to indicate that the match
is for a machine or SoC or SoC-family, but that may not be flexible
enough.
Essentially, all we really need to indicate is
