From: Stephen Warren <swarren@wwwdotorg.org>
To: wangyuhang <wangyuhang2014@gmail.com>
Cc: devicetree@vger.kernel.org, Tomasz Figa <tomasz.figa@gmail.com>,
linux-spi@vger.kernel.org, broonie@kernel.org,
linux-mtd@lists.infradead.org, pekon@ti.com,
sourav.poddar@ti.com
Subject: Re: [PATCH V2 2/2] spi: dual and quad support(device tree)
Date: Fri, 30 Aug 2013 15:26:44 -0600 [thread overview]
Message-ID: <52210E14.8020006@wwwdotorg.org> (raw)
In-Reply-To: <1377564603-4030-2-git-send-email-wangyuhang2014@gmail.com>
On 08/26/2013 06:50 PM, wangyuhang wrote:
> Add spi-tmax-nbits and spi-rmax-nbits for spi slave node.
> Modify the related dt document(spi-bus.txt)
> spi-tmax-nbits:Max number of bits slave will use for MOSI(writting)
> spi-rmax-nbits:Max number of bits slave will use for MISO(reading)
> Support for spi-tx/rmax-nbits in SPI framework has been picked[1].
> [1]: http://comments.gmane.org/gmane.linux.kernel.spi.devel/14420
> Commit Id:f477b7fb13df2b843997559ff34e87d054ba6538
> diff --git a/Documentation/devicetree/bindings/spi/spi-bus.txt b/Documentation/devicetree/bindings/spi/spi-bus.txt
> +- spi-tmax-nbits - (optional) Max number of bits slave will use for
> + MOSI(writting)
> +- spi-rmax-nbits - (optional) Max number of bits slave will use for
> + MISO(reading)
I would suggest the property names
spi-tx-num-wires, spi-rx-num-wires
or:
spi-tx-bus-width, spi-rx-bus-width (this option from Tomasz Figa on IRC)
Those name alone self-document their purpose much more clearly to me.
I would also change the descriptions a bit, resulting in the following
overall:
==========
- spi-tx-num-wires - (optional) The number of data wires that
transfer data from the SPI controller to the
SPI device. Defaults to 1 if not present.
- spi-rx-num-wires - (optional) The number of data wires that
transfer data from the SPI device to the
SPI controller. Defaults to 1 if not present.
==========
> +So if for example the slave has 4 wires for writting and 2 wires for reading,
> +and the spi-tx/rx-nbits property should be set as follows:
> +
> +spi-tmax-nbits = <4>;
> +spi-rmax-nbits = <2>;
> +
> +Now the value that spi-tmax-nbits and spi-rmax-nbits can receive is only
> +1(single), 2(dual) and 4(quad). If you don't set spi-tmax-nbits or spi-rmax-nbits,
> +spi_device mode will be set in single(1 wire) as default. Another point, if
> +property:spi-3wire is set, spi-t/rmax-nbits is forbidden to set to <2 or 4>,
> +otherwise, an errro will return.
I think most of that explanation can be removed if you use the text I
wrote above.
I'm not sure you should ban spi-3wire if those properties are specified;
can't all those properties be present together, if the num-wires are set
to 1? Actually, isn't spi-3write the default; what does that property mean?
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: wangyuhang <wangyuhang2014@gmail.com>
Cc: devicetree@vger.kernel.org, Tomasz Figa <tomasz.figa@gmail.com>,
linux-spi@vger.kernel.org, broonie@kernel.org,
linux-mtd@lists.infradead.org, pekon@ti.com,
sourav.poddar@ti.com
Subject: Re: [PATCH V2 2/2] spi: dual and quad support(device tree)
Date: Fri, 30 Aug 2013 15:26:44 -0600 [thread overview]
Message-ID: <52210E14.8020006@wwwdotorg.org> (raw)
In-Reply-To: <1377564603-4030-2-git-send-email-wangyuhang2014@gmail.com>
On 08/26/2013 06:50 PM, wangyuhang wrote:
> Add spi-tmax-nbits and spi-rmax-nbits for spi slave node.
> Modify the related dt document(spi-bus.txt)
> spi-tmax-nbits:Max number of bits slave will use for MOSI(writting)
> spi-rmax-nbits:Max number of bits slave will use for MISO(reading)
> Support for spi-tx/rmax-nbits in SPI framework has been picked[1].
> [1]: http://comments.gmane.org/gmane.linux.kernel.spi.devel/14420
> Commit Id:f477b7fb13df2b843997559ff34e87d054ba6538
> diff --git a/Documentation/devicetree/bindings/spi/spi-bus.txt b/Documentation/devicetree/bindings/spi/spi-bus.txt
> +- spi-tmax-nbits - (optional) Max number of bits slave will use for
> + MOSI(writting)
> +- spi-rmax-nbits - (optional) Max number of bits slave will use for
> + MISO(reading)
I would suggest the property names
spi-tx-num-wires, spi-rx-num-wires
or:
spi-tx-bus-width, spi-rx-bus-width (this option from Tomasz Figa on IRC)
Those name alone self-document their purpose much more clearly to me.
I would also change the descriptions a bit, resulting in the following
overall:
==========
- spi-tx-num-wires - (optional) The number of data wires that
transfer data from the SPI controller to the
SPI device. Defaults to 1 if not present.
- spi-rx-num-wires - (optional) The number of data wires that
transfer data from the SPI device to the
SPI controller. Defaults to 1 if not present.
==========
> +So if for example the slave has 4 wires for writting and 2 wires for reading,
> +and the spi-tx/rx-nbits property should be set as follows:
> +
> +spi-tmax-nbits = <4>;
> +spi-rmax-nbits = <2>;
> +
> +Now the value that spi-tmax-nbits and spi-rmax-nbits can receive is only
> +1(single), 2(dual) and 4(quad). If you don't set spi-tmax-nbits or spi-rmax-nbits,
> +spi_device mode will be set in single(1 wire) as default. Another point, if
> +property:spi-3wire is set, spi-t/rmax-nbits is forbidden to set to <2 or 4>,
> +otherwise, an errro will return.
I think most of that explanation can be removed if you use the text I
wrote above.
I'm not sure you should ban spi-3wire if those properties are specified;
can't all those properties be present together, if the num-wires are set
to 1? Actually, isn't spi-3write the default; what does that property mean?
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2013-08-30 21:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 0:50 [PATCH V2 1/2] spi: dual and quad support(device tree) wangyuhang
2013-08-27 0:50 ` wangyuhang
2013-08-27 0:50 ` [PATCH V2 2/2] " wangyuhang
2013-08-27 0:50 ` wangyuhang
2013-08-27 4:03 ` Gupta, Pekon
2013-08-27 4:03 ` Gupta, Pekon
2013-08-30 21:26 ` Stephen Warren [this message]
2013-08-30 21:26 ` Stephen Warren
2013-08-30 22:23 ` Mark Brown
2013-08-30 22:23 ` Mark Brown
2013-09-01 8:05 ` yuhang wang
2013-09-01 8:05 ` yuhang wang
2013-08-30 21:30 ` Tomasz Figa
2013-08-30 21:30 ` Tomasz Figa
2013-09-01 8:14 ` yuhang wang
2013-09-01 8:14 ` yuhang wang
2013-08-27 4:09 ` [PATCH V2 1/2] " Gupta, Pekon
2013-08-27 4:09 ` Gupta, Pekon
2013-08-27 4:58 ` yuhang wang
2013-08-27 4:58 ` yuhang wang
2013-08-27 7:56 ` yuhang wang
2013-08-27 7:56 ` yuhang wang
2013-08-27 8:37 ` Gupta, Pekon
2013-08-27 8:37 ` Gupta, Pekon
2013-08-30 21:20 ` Stephen Warren
2013-08-30 21:20 ` Stephen Warren
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=52210E14.8020006@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=pekon@ti.com \
--cc=sourav.poddar@ti.com \
--cc=tomasz.figa@gmail.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 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.