From: Tony Lindgren <tony@atomide.com>
To: Imre Deak <imre.deak@nokia.com>
Cc: omap-linux <linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH] SPI: add per transfer wordsize and speed parameter
Date: Fri, 12 May 2006 04:57:42 -0700 [thread overview]
Message-ID: <20060512115741.GI18115@atomide.com> (raw)
In-Reply-To: <1147433591.9837.14.camel@mammoth.research.nokia.com>
* Imre Deak <imre.deak@nokia.com> [060512 04:35]:
> [ This is at the moment only in Greg's queue, but would be nice to
> pre-merge it ]
>
> Some protocols (like one for some bitmap displays) require different clock
> speed or word size settings for each transfer in an SPI message. This adds
> those parameters to struct spi_transfer. They are to be used when they are
> nonzero; otherwise the defaults from spi_device are to be used.
>
> The patch also adds a setup_transfer callback to spi_bitbang, uses it for
> messages that use those overrides, and implements it so that the pure
> bitbanging code can help resolve any questions about how it should work.
Pushing today.
Tony
prev parent reply other threads:[~2006-05-12 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 11:33 [PATCH] SPI: add per transfer wordsize and speed parameter Imre Deak
2006-05-12 11:57 ` Tony Lindgren [this message]
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=20060512115741.GI18115@atomide.com \
--to=tony@atomide.com \
--cc=imre.deak@nokia.com \
--cc=linux-omap-open-source@linux.omap.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox