On Mon, 2007-05-07 at 22:00 -0700, David Brownell wrote:
> On Monday 07 May 2007, Bryan WU wrote:
>
> > currently, there are some duplicated data members in spi_device struct
> > spi_board_info struct. This two structs are confused driver writers and
> > boards driver users.
>
> How would that co
On 5/8/07, David Brownell <[EMAIL PROTECTED]> wrote:
On Monday 07 May 2007, Mike Frysinger wrote:
> On 4/25/07, David Brownell <[EMAIL PROTECTED]> wrote:
> > On Wednesday 25 April 2007, Mike Frysinger wrote:
> > > is there something obvious i'm missing ? seems to me that if the
> > > generic spi
On Monday 07 May 2007, Mike Frysinger wrote:
> On 4/25/07, David Brownell <[EMAIL PROTECTED]> wrote:
> > On Wednesday 25 April 2007, Mike Frysinger wrote:
>
> > > is there something obvious i'm missing ? seems to me that if the
> > > generic spi framework respects bits_per_word on a per-spi devic
On Monday 07 May 2007, Bryan WU wrote:
> currently, there are some duplicated data members in spi_device struct
> spi_board_info struct. This two structs are confused driver writers and
> boards driver users.
How would that confusion arise? Only arch/.../board-xxx.c writers
normally even see spi
On Mon, 2007-05-07 at 19:47 -0400, Mike Frysinger wrote:
> On 4/25/07, David Brownell <[EMAIL PROTECTED]> wrote:
> > On Wednesday 25 April 2007, Mike Frysinger wrote:
> > > the spi_device structure has a bits_per_word so that you can change
> > > the value on a per-device setting, yet the spi_board
On 4/25/07, David Brownell <[EMAIL PROTECTED]> wrote:
On Wednesday 25 April 2007, Mike Frysinger wrote:
> the spi_device structure has a bits_per_word so that you can change
> the value on a per-device setting, yet the spi_board_info structure
> does not ... this means that the bus-specific struc
On Wednesday 25 April 2007, Mike Frysinger wrote:
> the spi_device structure has a bits_per_word so that you can change
> the value on a per-device setting, yet the spi_board_info structure
> does not ... this means that the bus-specific structure has to have a
> bits_per_word member which the spi
the spi_device structure has a bits_per_word so that you can change
the value on a per-device setting, yet the spi_board_info structure
does not ... this means that the bus-specific structure has to have a
bits_per_word member which the spi bus driver will copy into the spi
device bits_per_word me
8 matches
Mail list logo
