From: Mark Brown <broonie@kernel.org>
To: yuhang wang <wangyuhang2014@gmail.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
spi-devel-general@lists.sourceforge.net,
Johannes Stezenbach <js@sig21.net>,
linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: SPI: DUAL/QUAD support
Date: Fri, 5 Jul 2013 11:12:04 +0100 [thread overview]
Message-ID: <20130705101204.GT27646@sirena.org.uk> (raw)
In-Reply-To: <CAHSAbzNBkZPFOfGHqFxZH_id=PFj=BmZ4Q302zGKeM-0yJBtHg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 686 bytes --]
On Fri, Jul 05, 2013 at 05:41:57PM +0800, yuhang wang wrote:
> Yes. I agree with you. This should be described in SPI level.
> So to SPI controller, if it has the ability to transfer in 2x or 4x, but
> what a pity no device can tell this info to it. No matter what the slave
> is and no matter whether they will use the spi transfer width member,
> firstly SPI controller should provide these members. If the slave do
> not set the member, that means the slave wants to communicate
> in 1 line traditionally.
Yes, it definitely makes sense to have this as a feature in the SPI
core. We just need a good API for it, which I think is mostly just
about working out what to call things.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-05 10:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 11:36 SPI: DUAL/QUAD support yuhang wang
2013-07-04 13:00 ` Johannes Stezenbach
2013-07-04 14:58 ` Thomas.Betker
2013-07-04 15:49 ` Mark Brown
2013-07-04 16:04 ` Thomas.Betker
2013-07-05 6:25 ` yuhang wang
2013-07-05 6:45 ` Gupta, Pekon
2013-07-05 7:35 ` Johannes Stezenbach
2013-07-05 7:41 ` Sourav Poddar
2013-07-05 8:04 ` Gupta, Pekon
2013-07-05 7:40 ` Sourav Poddar
2013-07-05 8:48 ` yuhang wang
2013-07-05 8:55 ` Sourav Poddar
2013-07-05 9:07 ` yuhang wang
2013-07-05 9:08 ` Sourav Poddar
2013-07-05 9:17 ` yuhang wang
2013-07-05 9:27 ` Sourav Poddar
2013-07-05 10:24 ` yuhang wang
2013-07-05 14:34 ` Johannes Stezenbach
2013-07-05 15:41 ` yuhang wang
2013-07-04 14:36 ` Mark Brown
2013-07-04 18:06 ` Johannes Stezenbach
2013-07-04 19:12 ` Mark Brown
2013-07-05 9:41 ` yuhang wang
2013-07-05 10:12 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-04 7:07 SPI : " 王宇航
2013-07-04 9:00 ` Mark Brown
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=20130705101204.GT27646@sirena.org.uk \
--to=broonie@kernel.org \
--cc=grant.likely@secretlab.ca \
--cc=js@sig21.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=spi-devel-general@lists.sourceforge.net \
--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