From: Stephen Boyd <sboyd@kernel.org>
To: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh@kernel.org>,
Sukrut Bellary <sbellary@baylibre.com>
Cc: Sukrut Bellary <sbellary@baylibre.com>,
Tero Kristo <kristo@kernel.org>,
Kevin Hilman <khilman@baylibre.com>,
Andreas Kemnade <andreas@kemnade.info>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: clock: ti: Convert autoidle binding to yaml
Date: Wed, 11 Jun 2025 11:17:24 -0500 [thread overview]
Message-ID: <174965864472.7717.17541212965175325191@lazor> (raw)
In-Reply-To: <20250516081612.767559-2-sbellary@baylibre.com>
Quoting Sukrut Bellary (2025-05-16 03:16:10)
> Autoidle clock is not an individual clock; it is always a derivate of some
> basic clock like a gate, divider, or fixed-factor. This binding will be
> referred in ti,divider-clock.yaml, and ti,fixed-factor-clock.yaml.
>
> As all clocks don't support the autoidle feature e.g.,
> in DRA77xx/AM57xx[1], dpll_abe_x2* and dpll_per_x2 don't have
> autoidle, remove required properties from the binding.
>
> Add the creator of the original binding as a maintainer.
>
> [1] https://www.ti.com/lit/ug/spruhz6l/spruhz6l.pdf
>
> Signed-off-by: Sukrut Bellary <sbellary@baylibre.com>
> ---
Applied to clk-next
next prev parent reply other threads:[~2025-06-11 16:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 8:16 [PATCH v2 0/3] dt-bindings: clock: ti: convert to yaml Sukrut Bellary
2025-05-16 8:16 ` [PATCH v2 1/3] dt-bindings: clock: ti: Convert autoidle binding " Sukrut Bellary
2025-05-16 9:56 ` Rob Herring (Arm)
2025-06-11 16:17 ` Stephen Boyd [this message]
2025-05-16 8:16 ` [PATCH v2 2/3] dt-bindings: clock: ti: Convert fixed-factor-clock " Sukrut Bellary
2025-06-11 16:17 ` Stephen Boyd
2025-05-16 8:16 ` [PATCH v2 3/3] dt-bindings: clock: ti: add ti,autoidle.yaml reference Sukrut Bellary
2025-06-11 16:17 ` Stephen Boyd
2025-05-20 19:55 ` [PATCH v2 0/3] dt-bindings: clock: ti: convert to yaml 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=174965864472.7717.17541212965175325191@lazor \
--to=sboyd@kernel.org \
--cc=andreas@kemnade.info \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sbellary@baylibre.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