From: Kuldeep Singh <singh.kuldeep87k@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: Mark Brown <broonie@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-spi@vger.kernel.org,
devicetree@vger.kernel.org, Robin Murphy <robin.murphy@arm.com>,
Linus Walleij <linus.walleij@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: spi: Update clocks property for ARM pl022
Date: Fri, 11 Mar 2022 08:25:02 +0530 [thread overview]
Message-ID: <20220311025502.GB54098@9a2d8922b8f1> (raw)
In-Reply-To: <Yip2MZdQNjMz/Cos@robh.at.kernel.org>
On Thu, Mar 10, 2022 at 04:05:37PM -0600, Rob Herring wrote:
> On Tue, Mar 08, 2022 at 12:51:24PM +0530, Kuldeep Singh wrote:
> > Add missing minItems property to clocks in ARM pl022 bindings.
> >
> > This helps in resolving below warnings:
> > clocks: [[4]] is too short
> > clock-names: ['apb_pclk'] is too short
>
> Again, the error is in the dts files, not the schema.
Rob, kindly note this series number is deprecated and I have sent v3
version some time back. Here's the link:
https://lore.kernel.org/linux-spi/20220309171847.5345-1-singh.kuldeep87k@gmail.com/T/#u
>
>
> There's 2 possible answers. First, both clock inputs use the same source
> clock. That's an easy fix. List the clock twice. Second, one clock is
> not described in DT or visible to s/w. It still has to be in the h/w and
> could be described as a 'fixed-clock'. A DT should either be all in with
> clocks or not use the clock binding IMO. Describing some clocks and not
> others is not a good solution.
>
> For example, let's look at bcm-cygnus as one of the single clock
> examples. The first thing I notice is there is a apb_pclk already
> defined. The pl330 uses it. The watchdog (also Primecell) lists the
> source clock twice. So what should pl022 be? IDK, ask the Broadcom
> folks. If they don't know, then list the source clock twice. That's
> effectively no change from what we have now.
Yes, I took motivation from sp805 watchdog(primecell) while resolving DT
conflicts. I found LG and amd seattle platform with single clock in DT
for which I have sent patches. Link is below:
https://lore.kernel.org/linux-devicetree/CAL_Jsq+k+ridWTkdy4xwTC7VxUTU8tu+Q2BA9kbQVA222PWvZw@mail.gmail.com/
Moreover, I observed that clocks and clock-names are not required
properties for pl022. I am wondering reason behind the same when you
first made changes. Any specific reason not adding them which I am not
aware of or it just got missed?
- Kuldeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-11 2:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 7:21 [PATCH v2 1/2] dt-bindings: spi: Update clocks property for ARM pl022 Kuldeep Singh
2022-03-08 7:21 ` [PATCH v2 2/2] dt-bindings: spi: Update clock-names " Kuldeep Singh
2022-03-10 22:08 ` Rob Herring
2022-03-11 2:57 ` Kuldeep Singh
2022-03-08 8:27 ` [PATCH v2 1/2] dt-bindings: spi: Update clocks " Krzysztof Kozlowski
2022-03-09 13:57 ` Kuldeep Singh
2022-03-10 22:05 ` Rob Herring
2022-03-11 2:55 ` Kuldeep Singh [this message]
2022-03-11 3:31 ` Kuldeep Singh
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=20220311025502.GB54098@9a2d8922b8f1 \
--to=singh.kuldeep87k@gmail.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.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