From: Mark Brown <broonie@kernel.org>
To: wangyuhang <wangyuhang2014@gmail.com>
Cc: linux-mtd@lists.infradead.org, pekon@ti.com, linux-spi@vger.kernel.org
Subject: Re: [PATCH V2] spi: dual and quad support(add single macro)
Date: Thu, 29 Aug 2013 13:25:00 +0100 [thread overview]
Message-ID: <20130829122500.GC10783@sirena.org.uk> (raw)
In-Reply-To: <1377738110-4219-1-git-send-email-wangyuhang2014@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
On Thu, Aug 29, 2013 at 09:01:50AM +0800, wangyuhang wrote:
> fix two things in patch:
> commit id:f477b7fb13df2b843997559ff34e87d054ba6538
> 1.Add SPI_TX_SINGLE and SPI_RX_SINGLE to specify SINGLE mode.
> Instead of using default value in mode.
> 2.Delete a "return" when commit the patch to a new kernel version
> by mistake. So recover it.
These two changes aren't related to each other so should be sent as two
separate patches.
> @@ -89,8 +89,12 @@ struct spi_device {
> #define SPI_READY 0x80 /* slave pulls low to pause */
> #define SPI_TX_DUAL 0x100 /* transmit with 2 wires */
> #define SPI_TX_QUAD 0x200 /* transmit with 4 wires */
> +/* transmit with 1 wire(not using dual-tx and quad-tx) */
> +#define SPI_TX_SINGLE ~(SPI_TX_DUAL | SPI_TX_QUAD)
> #define SPI_RX_DUAL 0x400 /* receive with 2 wires */
> #define SPI_RX_QUAD 0x800 /* receive with 4 wires */
> +/* receive with 1 wire(not using dual-rx and quad-rx) */
> +#define SPI_RX_SINGLE ~(SPI_RX_DUAL | SPI_RX_QUAD)
These don't look right, they're going to set all bits which is going to
interfere with all the other flags. Why do we need this define at all?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-08-29 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 1:01 [PATCH V2] spi: dual and quad support(add single macro) wangyuhang
2013-08-29 12:25 ` Mark Brown [this message]
2013-08-29 12:45 ` yuhang wang
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=20130829122500.GC10783@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=pekon@ti.com \
--cc=wangyuhang2014@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox