From: Rob Herring <robh@kernel.org>
To: Baolin Wang <baolin.wang@linaro.org>
Cc: Trent Piepho <tpiepho@impinj.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"orsonzhai@gmail.com" <orsonzhai@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"zhang.lyra@gmail.com" <zhang.lyra@gmail.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"lanqing.liu@spreadtrum.com" <lanqing.liu@spreadtrum.com>
Subject: Re: [PATCH 1/2] dt-bindings: spi: Add Spreadtrum SPI controller documentation
Date: Tue, 14 Aug 2018 14:27:20 -0600 [thread overview]
Message-ID: <20180814202720.GB26606@rob-hp-laptop> (raw)
In-Reply-To: <CAMz4kuKwfBB8-8o5s8FQadFSFiD8KU=qNZYQjCWOfc-QpuVRSw@mail.gmail.com>
On Thu, Aug 09, 2018 at 11:03:11AM +0800, Baolin Wang wrote:
> Hi Trent,
>
> On 9 August 2018 at 02:57, Trent Piepho <tpiepho@impinj.com> wrote:
> > On Wed, 2018-08-08 at 11:54 +0100, Mark Brown wrote:
> >> On Wed, Aug 08, 2018 at 06:35:28PM +0800, Baolin Wang wrote:
> >> > On 8 August 2018 at 17:50, Mark Brown <broonie@kernel.org> wrote:
> >> > > Right, I don't think we added this yet (if we did I can't see
> >> > > it). I'd
> >> > > add a new field to spi_transfer for this, then other controllers
> >> > > with
> >> > > the same support can implement it as well and drivers can start
> >> > > using
> >> > > it too.
> >> > OK. So I will name the new filed as 'word_delay', is it OK for you?
> >>
> >> Sounds good, yes.
> >
> > Should it be in µs like the existing iter-transfer delay? I think
> > perhaps units of cycles of the SPI clock make more sense?
>
> Since some SPI controllers just want some interval values (neither µs
> unit nor cycles unit ) set into hardware, and the hardware will
> convert to the correct delay time automatically. So I did not force
> 'word_delay' unit as µs or cycle, and just let the slave devices
> decide the unit which depends on the SPI hardware requirement.
This needs to be defined units in DT, not decided by each controller.
The controller capabilities just affect what are valid values (or what
the resolution is).
Rob
next prev parent reply other threads:[~2018-08-14 20:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 10:43 [PATCH 1/2] dt-bindings: spi: Add Spreadtrum SPI controller documentation Baolin Wang
2018-08-07 10:43 ` [PATCH 2/2] spi: sprd: Add SPI driver for Spreadtrum SC9860 Baolin Wang
2018-08-07 14:24 ` Mark Brown
2018-08-08 2:45 ` Baolin Wang
2018-08-08 9:31 ` Mark Brown
2018-08-08 9:33 ` Baolin Wang
2018-08-07 17:10 ` Trent Piepho
2018-08-08 3:19 ` Baolin Wang
2018-08-08 19:08 ` Trent Piepho
2018-08-09 3:23 ` Baolin Wang
2018-08-07 13:41 ` [PATCH 1/2] dt-bindings: spi: Add Spreadtrum SPI controller documentation Mark Brown
2018-08-08 2:26 ` Baolin Wang
2018-08-08 9:50 ` Mark Brown
2018-08-08 10:35 ` Baolin Wang
2018-08-08 10:54 ` Mark Brown
2018-08-08 11:07 ` Baolin Wang
2018-08-08 18:57 ` Trent Piepho
2018-08-09 3:03 ` Baolin Wang
2018-08-14 20:27 ` Rob Herring [this message]
2018-08-15 2:17 ` Baolin Wang
2018-08-14 20:21 ` Rob Herring
2018-08-15 1:44 ` Baolin 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=20180814202720.GB26606@rob-hp-laptop \
--to=robh@kernel.org \
--cc=baolin.wang@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lanqing.liu@spreadtrum.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=orsonzhai@gmail.com \
--cc=tpiepho@impinj.com \
--cc=zhang.lyra@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