From: luhua xu <luhua.xu@mediatek.com>
To: Mark Brown <broonie@kernel.org>
Cc: Kate Stewart <kstewart@linuxfoundation.org>,
wsd_upstream@mediatek.com, Leilk Liu <leilk.liu@mediatek.com>,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Enrico Weigelt <info@metux.net>,
Allison Randal <allison@lohutok.net>
Subject: Re: [PATCH 2/2] spi: mediatek: add cs timing configuration support
Date: Wed, 20 Nov 2019 17:31:23 +0800 [thread overview]
Message-ID: <1574242283.27063.5.camel@mbjsdccf07> (raw)
In-Reply-To: <20191119181930.GF3634@sirena.org.uk>
On Tue, 2019-11-19 at 18:19 +0000, Mark Brown wrote:
> On Mon, Nov 18, 2019 at 12:57:17PM +0800, Luhua Xu wrote:
> > Add configure SPI CS setup/hold/idle delays in terms
> > of clk count support, and use one period of current
> > spi speed as default if setup/hold/idle not indicated.
>
> We have added a generic way to specify delays like this via the
> set_cs_timing() operation and related fields in the spi_device struct
> which operate in terms of spi_delay - Alexandru Ardelean added them
> recently. This supports both times and clock cycles as units so should
> fit with what your hardware can do, the interface is new though so there
> may be soem rough edges to worry about.
I find the patch today. It's really a better idear.
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
prev parent reply other threads:[~2019-11-20 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 4:57 [PATCH 0/2] spi CS customization support Luhua Xu
2019-11-18 4:57 ` [PATCH 1/2] spi: mediatek: add SPI_CS_HIGH support Luhua Xu
2019-11-18 17:49 ` Applied "spi: mediatek: add SPI_CS_HIGH support" to the spi tree Mark Brown
2019-11-18 4:57 ` [PATCH 2/2] spi: mediatek: add cs timing configuration support Luhua Xu
2019-11-19 18:19 ` Mark Brown
2019-11-20 9:31 ` luhua xu [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=1574242283.27063.5.camel@mbjsdccf07 \
--to=luhua.xu@mediatek.com \
--cc=allison@lohutok.net \
--cc=broonie@kernel.org \
--cc=info@metux.net \
--cc=kstewart@linuxfoundation.org \
--cc=leilk.liu@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=tglx@linutronix.de \
--cc=wsd_upstream@mediatek.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;
as well as URLs for NNTP newsgroup(s).