From: Rob Herring <robh+dt@kernel.org>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: Mark Brown <broonie@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
linux-spi <linux-spi@vger.kernel.org>,
devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/2] dt-bindings: spi: Document binding for generic SPI multiplexer
Date: Fri, 31 Jan 2020 08:12:03 -0600 [thread overview]
Message-ID: <CAL_JsqLO4DT1s-q_5n23pLJw7PgnVNC6W3aAwkLFB_QdtV721w@mail.gmail.com> (raw)
In-Reply-To: <20200131023433.12133-2-chris.packham@alliedtelesis.co.nz>
On Thu, Jan 30, 2020 at 8:34 PM Chris Packham
<chris.packham@alliedtelesis.co.nz> wrote:
>
> Add binding documentation for the spi-mux driver. This allows a generic
> multiplexer to be used to provide access to multiple SPI devices.
>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> ---
>
> Notes:
> Changes in v3:
> - make dt_binding_check clean (properly this time)
>
> Changes in v2:
> - update license
> - make dt_binding_check clean
>
> .../devicetree/bindings/spi/spi-mux.yaml | 89 +++++++++++++++++++
> 1 file changed, 89 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/spi/spi-mux.yaml
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-01-31 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 2:34 [PATCH v4 0/2] SPI bus multiplexing Chris Packham
[not found] ` <20200131023433.12133-1-chris.packham-6g8wRflRTwXFdCa3tKVlE6U/zSkkHjvu@public.gmane.org>
2020-01-31 2:34 ` [PATCH v4 1/2] dt-bindings: spi: Document binding for generic SPI multiplexer Chris Packham
2020-01-31 14:12 ` Rob Herring [this message]
2020-01-31 2:34 ` [PATCH v4 2/2] spi: Add " Chris Packham
[not found] ` <20200131023433.12133-3-chris.packham-6g8wRflRTwXFdCa3tKVlE6U/zSkkHjvu@public.gmane.org>
2020-02-03 9:50 ` Andy Shevchenko
[not found] ` <CAHp75VfT=KNM6J1bP5cPsLw7Z776opcB9Kf6qhNCZukY-7g=pQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-02-03 21:11 ` Chris Packham
[not found] ` <86509a5e6656c4f560ee6f6514ab00a232994957.camel-6g8wRflRTwXFdCa3tKVlE6U/zSkkHjvu@public.gmane.org>
2020-02-04 11:07 ` Andy Shevchenko
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=CAL_JsqLO4DT1s-q_5n23pLJw7PgnVNC6W3aAwkLFB_QdtV721w@mail.gmail.com \
--to=robh+dt@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=broonie@kernel.org \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mark.rutland@arm.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).