From: Rob Herring <robh@kernel.org>
To: Alexandru Ardelean <alexandru.ardelean@analog.com>
Cc: linux-spi@vger.kernel.org, broonie@kernel.org,
andy.shevchenko@gmail.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
dragos.bogdan@analog.com
Subject: Re: [PATCH v4 3/3] spi: dt-bindings: document zero value for spi-{rx,tx}-bus-width properties
Date: Wed, 9 Dec 2020 14:13:45 -0600 [thread overview]
Message-ID: <20201209201345.GA864933@robh.at.kernel.org> (raw)
In-Reply-To: <20201203140531.74470-3-alexandru.ardelean@analog.com>
On Thu, 03 Dec 2020 16:05:31 +0200, Alexandru Ardelean wrote:
> Following a change to the SPI framework, providing a value of zero for
> 'spi-rx-bus-width' and 'spi-tx-bus-width' is now possible and will
> essentially mean that no RX or TX is allowed.
>
> Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
> ---
>
> Changelog v3 -> v4:
> * https://lore.kernel.org/linux-spi/20201127130834.136348-3-alexandru.ardelean@analog.com/
> * fix typos
>
> Documentation/devicetree/bindings/spi/spi-controller.yaml | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-12-09 20:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 14:05 [PATCH v4 1/3] spi: uapi: unify SPI modes into a single spi.h header Alexandru Ardelean
2020-12-03 14:05 ` [PATCH v4 2/3] spi: Add SPI_NO_TX/RX support Alexandru Ardelean
2020-12-03 14:10 ` Andy Shevchenko
2020-12-03 14:27 ` Andy Shevchenko
2020-12-03 14:24 ` Andy Shevchenko
2020-12-03 14:05 ` [PATCH v4 3/3] spi: dt-bindings: document zero value for spi-{rx,tx}-bus-width properties Alexandru Ardelean
2020-12-09 20:13 ` Rob Herring [this message]
2020-12-03 14:14 ` [PATCH v4 1/3] spi: uapi: unify SPI modes into a single spi.h header 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=20201209201345.GA864933@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=alexandru.ardelean@analog.com \
--cc=andy.shevchenko@gmail.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dragos.bogdan@analog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.