From: Kousik Sanagavarapu <five231003@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>,
Javier Carrasco <javier.carrasco.cruz@gmail.com>
Subject: Re: [RFC PATCH] spi: dt-bindings: ti,qspi: convert to dtschema
Date: Mon, 29 Apr 2024 12:40:31 +0530 [thread overview]
Message-ID: <Zi9H5371PrJtIKVy@five231003> (raw)
In-Reply-To: <59fe75b6-a4a4-4c90-a3c4-c8a4b539e879@kernel.org>
On Mon, Apr 29, 2024 at 07:07:38AM +0200, Krzysztof Kozlowski wrote:
> On 28/04/2024 08:58, Kousik Sanagavarapu wrote:
> > Convert txt binding of TI's qspi controller (found on their omap SoCs) to
> > dtschema to allow for validation.
[...]
> > + spi-max-frequency:
> > + description: Maximum SPI clocking speed of the controller in Hz.
> > + $ref: /schemas/types.yaml#/definitions/uint32
>
>
> Are you sure that's actually needed? That's not a property of controller.
[...]
> > + num-cs = <4>;
> > + spi-max-frequency = <48000000>;
>
> Drop. Are you sure driver parses it?
The driver does parse it though. Looking at
drivers/spi/spi-ti-qspi.c::ti_qspi_probe(),
if (!of_property_read_u32(np, "spi-max-frequency", &max_freq))
host->max_speed_hz = max_freq;
So I included it in the dtschema as well. Please let me know if
including it in the dtschema in this case is wrong.
Thanks
next prev parent reply other threads:[~2024-04-29 7:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 6:58 [RFC PATCH] spi: dt-bindings: ti,qspi: convert to dtschema Kousik Sanagavarapu
2024-04-29 5:07 ` Krzysztof Kozlowski
2024-04-29 7:10 ` Kousik Sanagavarapu [this message]
2024-04-29 7:25 ` Krzysztof Kozlowski
2024-04-29 16:26 ` Rob Herring
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=Zi9H5371PrJtIKVy@five231003 \
--to=five231003@gmail.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=javier.carrasco.cruz@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh@kernel.org \
--cc=skhan@linuxfoundation.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).