From: Patrice CHOTARD <patrice.chotard@foss.st.com>
To: Mark Brown <broonie@kernel.org>
Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>,
<linux-spi@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <christophe.kerello@foss.st.com>
Subject: Re: [PATCH v2 1/2] spi: stm32_qspi: Add transfer_one_message() spi callback
Date: Wed, 10 Aug 2022 15:31:59 +0200 [thread overview]
Message-ID: <38200a6f-fdc1-fa94-7bc6-91ca528235ed@foss.st.com> (raw)
In-Reply-To: <YvOxOg0vXSGrZLfP@sirena.org.uk>
On 8/10/22 15:23, Mark Brown wrote:
> On Wed, Aug 10, 2022 at 03:15:08PM +0200, Patrice CHOTARD wrote:
>> On 8/10/22 15:06, Mark Brown wrote:
>
>>> Do we need to add something to the DT bindings to indicate that
>>> parallel-memories is valid?
>
>> You mean in the st,stm32-qspi.yaml DT binding file ? Right i think it could be preferable to add it.
>
> Yes. Though I'm not clear if the bindings actually want to enforce it
> there, it's a device level property not a controller level one so it
> might not be something where controller support gets validated.
Ah yes, i see, parallel-memories should not be used in our qspi controller node.
So i can't reuse parallel-memories for my purpose.
So i need to add a new proprietary property at controller level as done in the v1 ?
next prev parent reply other threads:[~2022-08-10 13:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 9:32 [PATCH v2 0/2] spi: stm32_qspi: use QSPI bus as 8 lines communication channel patrice.chotard
2022-08-10 9:32 ` [PATCH v2 1/2] spi: stm32_qspi: Add transfer_one_message() spi callback patrice.chotard
2022-08-10 13:06 ` Mark Brown
2022-08-10 13:15 ` Patrice CHOTARD
2022-08-10 13:23 ` Mark Brown
2022-08-10 13:31 ` Patrice CHOTARD [this message]
2022-08-10 13:40 ` Mark Brown
2022-08-10 13:52 ` Patrice CHOTARD
2022-08-10 13:57 ` Mark Brown
2022-08-10 9:32 ` [PATCH v2 2/2] ARM: dts: stm32: Create separate pinmux for qspi cs pin in stm32mp15-pinctrl.dtsi patrice.chotard
2022-08-22 16:05 ` (subset) [PATCH v2 0/2] spi: stm32_qspi: use QSPI bus as 8 lines communication channel 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=38200a6f-fdc1-fa94-7bc6-91ca528235ed@foss.st.com \
--to=patrice.chotard@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=broonie@kernel.org \
--cc=christophe.kerello@foss.st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.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).