All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: spi-devel-general@lists.sourceforge.net
Cc: "Mike Frysinger" <vapier.adi@gmail.com>,
	"Wu, Bryan" <Bryan.Wu@analog.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [spi-devel-general] adding bits_per_word to struct spi_board_info to mirror struct spi_device
Date: Wed, 25 Apr 2007 08:13:30 -0700	[thread overview]
Message-ID: <200704250813.30999.david-b@pacbell.net> (raw)
In-Reply-To: <8bd0f97a0704250305qe6175cdm8e1a0cd7844f67bc@mail.gmail.com>

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 bus driver will copy into the spi
> device bits_per_word member

Actually that's more likely a driver-specific characteristic than
something related to board wiring/configuration ... a characteristic
of the particular protocol requests being made.  That's why for
example bits_per_word has a per-transfer override, and drivers are
able to call spi_setup(spi).


> is there something obvious i'm missing ?  seems to me that if the
> generic spi framework respects bits_per_word on a per-spi device
> basis, then it should be exposed in the generic info structure so that
> the setting can be tracked in the boards file ...

The initial driver set didn't need it, that's all.  ISTR someone
else pointed out this quirk, but never provided a patch to resolve
the issue.

- Dave

  reply	other threads:[~2007-04-25 15:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-25 10:05 adding bits_per_word to struct spi_board_info to mirror struct spi_device Mike Frysinger
2007-04-25 15:13 ` David Brownell [this message]
2007-05-07 23:47   ` [spi-devel-general] " Mike Frysinger
2007-05-08  3:48     ` Bryan WU
2007-05-08  5:00       ` David Brownell
2007-05-08  7:31         ` Bryan WU
2007-05-08  4:53     ` David Brownell
2007-05-08  5:24       ` Mike Frysinger

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=200704250813.30999.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=Bryan.Wu@analog.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spi-devel-general@lists.sourceforge.net \
    --cc=vapier.adi@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.