The gpiommc configfs context structure needs locking, as configfs
does not lock access between files (or if it does, we shouldn't
depend on this to magically happen).
Signed-off-by: Michael Buesch <[EMAIL PROTECTED]>
Index: linux-next/drivers/mmc/hos
The configfs API changed in linux-next. This patch fixes gpiommc
to use the new API. This fixes a compiler warning.
Signed-off-by: Michael Buesch <[EMAIL PROTECTED]>
---
Warning remained unoticed when porting the stuff from 2.6.25 to linux-next.
Index: linux-next/drivers/mmc/host/gpi
On Monday 21 July 2008 22:41:35 David Brownell wrote:
> So what this driver adds is mostly a userspace interface, yes?
Mostly. It also provides a simple platform device.
> If so, please refocus the descriptions a bit more on that;
> it's not actually a "GPIO based MMC/SD driver"; it's really
> a
On Monday 28 July 2008 01:30:07 David Brownell wrote:
> > How to?
>
> Simplest to just rip out the support for using one! And in any case:
> as a rule, any delay should be a function of the target bus speed.
Well, that wasn't exactly an answer to my question. ;)
So setting boardinfo->max_speed_h
101 - 104 of 104 matches
Mail list logo
