From: Mark Brown <broonie@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jonas Bonn <jonas@norrbonn.se>,
Baolin Wang <baolin.wang@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-spi <linux-spi@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
DTML <devicetree@vger.kernel.org>
Subject: Re: [PATCH 1/2] spi: support inter-word delay requirement for devices
Date: Mon, 28 Jan 2019 11:47:57 +0000 [thread overview]
Message-ID: <20190128114757.GA11699@sirena.org.uk> (raw)
In-Reply-To: <CAMuHMdXQONq1UFuFHwny_xfAtxY7sOv2K3yi2i9T22OovMqFhw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 612 bytes --]
On Mon, Jan 28, 2019 at 08:41:05AM +0100, Geert Uytterhoeven wrote:
> On Sat, Jan 26, 2019 at 4:40 PM Jonas Bonn <jonas@norrbonn.se> wrote:
> > spi-3wire: again, only set by MAXIM DS-1302 which always needs this
> > setting; driver could set this
> For DS1302, this is probable true.
> Some devices may support both 4-wire or 3-wire mode?
IIRC yes.
> > Yeah, that one make sense. But if the DT is only overriding the maximum
> > device frequency that the driver should otherwise be setting, why is
> > spi-max-frequency a _required_ property?
> That's a good question. Legacy?
It's a documentation error.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-28 11:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190125114429.20066-1-jonas@norrbonn.se>
2019-01-25 11:44 ` [PATCH 1/2] spi: support inter-word delay requirement for devices Jonas Bonn
2019-01-25 11:53 ` Baolin Wang
2019-01-25 12:06 ` Jonas Bonn
2019-01-25 17:47 ` Mark Brown
2019-01-25 17:50 ` Mark Brown
2019-01-26 7:52 ` Jonas Bonn
2019-01-26 10:25 ` Geert Uytterhoeven
2019-01-26 15:40 ` Jonas Bonn
2019-01-28 7:41 ` Geert Uytterhoeven
2019-01-28 11:47 ` Mark Brown [this message]
2019-01-28 11:51 ` Jonas Bonn
2019-01-28 11:54 ` Geert Uytterhoeven
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=20190128114757.GA11699@sirena.org.uk \
--to=broonie@kernel.org \
--cc=baolin.wang@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=jonas@norrbonn.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
/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).