From: "Raphaël Gallais-Pou" <rgallaispou@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: st: add buswidth property to stm32f429-disco
Date: Mon, 3 Jul 2023 05:25:08 +0200 [thread overview]
Message-ID: <4aba0e4a-87f0-1810-bf4d-a2f278e51e8b@gmail.com> (raw)
In-Reply-To: <11ec64ad-8fb8-e94d-2019-d3deb399084b@linaro.org>
Hi,
Le 02/07/2023 à 22:14, Krzysztof Kozlowski a écrit :
> On 02/07/2023 12:35, Raphael Gallais-Pou wrote:
>> The ili9341 is left without a mandatory buswidth to properly communicate
>> between the SI bus and the display. Add the device-tree property.
>>
>> Signed-off-by: Raphael Gallais-Pou <rgallaispou@gmail.com>
>> ---
>> arch/arm/boot/dts/stm32f429-disco.dts | 1 +
>
> There is no such file. Please rebase on recent Linux.
Yes, indeed. I forgot to pull, I'm sorry.
>
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/arch/arm/boot/dts/stm32f429-disco.dts b/arch/arm/boot/dts/stm32f429-disco.dts
>> index 3b81228d46a2..5eaf95afc8c7 100644
>> --- a/arch/arm/boot/dts/stm32f429-disco.dts
>> +++ b/arch/arm/boot/dts/stm32f429-disco.dts
>> @@ -197,6 +197,7 @@ display: display@1{
>> spi-3wire;
>> spi-max-frequency = <10000000>;
>> dc-gpios = <&gpiod 13 0>;
>> + buswidth = <8>;
>
> There is no such spi property.
While I agree with you, I saw in staging drivers that this property was
fetch in the device-tree by the fbtft core.
Should I document those in or try to do it another way ?
>
> Best regards,
> Krzysztof
>
Thanks,
Raphaël
next prev parent reply other threads:[~2023-07-03 3:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 10:35 Raphael Gallais-Pou
2023-07-02 20:14 ` Krzysztof Kozlowski
2023-07-03 3:25 ` Raphaël Gallais-Pou [this message]
2023-07-03 7:13 ` Krzysztof Kozlowski
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=4aba0e4a-87f0-1810-bf4d-a2f278e51e8b@gmail.com \
--to=rgallaispou@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.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
all inboxes | Powered by JetHome®