From: Vladimir Oltean <olteanv@gmail.com>
To: Frank Li <Frank.Li@nxp.com>
Cc: Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
imx@lists.linux.dev
Subject: Re: [PATCH v4 3/3] arm64: dts: fsl-ls1043a-rdb: use common spi-cs-setup(hold)-delay-ns
Date: Tue, 25 Jun 2024 15:34:13 +0300 [thread overview]
Message-ID: <20240625123413.kksqh4zbi5bzfaan@skbuf> (raw)
In-Reply-To: <20240624-ls_qspi-v4-3-3d1c6f5005bf@nxp.com> <20240624-ls_qspi-v4-3-3d1c6f5005bf@nxp.com>
On Mon, Jun 24, 2024 at 02:55:29PM -0400, Frank Li wrote:
> Use SPI common properties 'spi-cs-setup-delay-ns' and
> 'spi-cs-hold-delay-ns', mark private properties 'fsl,spi-cs-sck-delay'
> and 'fsl,spi-sck-cs-delay' as deprecated.
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
> Chang from v3 to v4
> - fix typo at commit message
> - use comments:
> Standard CS timing
> properties replace the deprecated vendor variants below
> ---
Reviewed-by: Vladimir Oltean <olteanv@gmail.com>
next prev parent reply other threads:[~2024-06-25 12:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 18:55 [PATCH v4 0/3] spi: fsl-dspi: Convert to yaml format and use common SPI property Frank Li
2024-06-24 18:55 ` [PATCH v4 1/3] spi: fsl-dspi: use common proptery 'spi-cs-setup(hold)-delay-ns' Frank Li
2024-06-25 12:32 ` Vladimir Oltean
2024-06-24 18:55 ` [PATCH v4 2/3] spi: dt-bindings: fsl-dspi: Convert to yaml format Frank Li
2024-06-24 21:02 ` Rob Herring (Arm)
2024-06-25 12:33 ` Vladimir Oltean
2024-06-24 18:55 ` [PATCH v4 3/3] arm64: dts: fsl-ls1043a-rdb: use common spi-cs-setup(hold)-delay-ns Frank Li
2024-06-25 12:34 ` Vladimir Oltean [this message]
2024-06-27 9:56 ` Shawn Guo
2024-07-01 14:52 ` (subset) [PATCH v4 0/3] spi: fsl-dspi: Convert to yaml format and use common SPI property Mark Brown
2024-07-01 15:24 ` Frank Li
2024-07-01 15:28 ` Mark Brown
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=20240625123413.kksqh4zbi5bzfaan@skbuf \
--to=olteanv@gmail.com \
--cc=Frank.Li@nxp.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh@kernel.org \
--cc=shawnguo@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).