devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Kemnade <andreas@kemnade.info>
To: Sukrut Bellary <sbellary@baylibre.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Tero Kristo <kristo@kernel.org>,
	Kevin Hilman <khilman@baylibre.com>,
	linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] dt-bindings: clock: ti: add ti,autoidle.yaml reference
Date: Sat, 5 Apr 2025 21:49:04 +0200	[thread overview]
Message-ID: <20250405214904.0b07b26f@akair> (raw)
In-Reply-To: <20250404014500.2789830-5-sbellary@baylibre.com>

Am Thu,  3 Apr 2025 18:45:00 -0700
schrieb Sukrut Bellary <sbellary@baylibre.com>:

> ti,divider-clock uses properties from ti,autoidle.
> 
> As we are converting autoidle binding to ti,autoidle.yaml,
> fix the reference here.
> 
> Add dual license.
> 
> Signed-off-by: Sukrut Bellary <sbellary@baylibre.com>
> ---
>  .../bindings/clock/ti/ti,divider-clock.yaml   | 24 ++++---------------
>  1 file changed, 5 insertions(+), 19 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/clock/ti/ti,divider-clock.yaml b/Documentation/devicetree/bindings/clock/ti/ti,divider-clock.yaml
> index 3fbe236eb565..aba879ae302d 100644
> --- a/Documentation/devicetree/bindings/clock/ti/ti,divider-clock.yaml
> +++ b/Documentation/devicetree/bindings/clock/ti/ti,divider-clock.yaml
> @@ -1,4 +1,4 @@
> -# SPDX-License-Identifier: GPL-2.0-only
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
>  %YAML 1.2
>  ---
>  $id: http://devicetree.org/schemas/clock/ti/ti,divider-clock.yaml#
> @@ -55,9 +55,10 @@ description: |
>    is missing it is the same as supplying a zero shift.
>  
>    This binding can also optionally provide support to the hardware autoidle
> -  feature, see [1].
> +  feature.
>  
> -  [1] Documentation/devicetree/bindings/clock/ti/autoidle.txt
> +allOf:
> +  - $ref: /schemas/clock/ti/ti,autoidle.yaml#
>  
>  properties:
>    compatible:
> @@ -97,7 +98,6 @@ properties:
>      minimum: 1
>      default: 1
>  
> -
>    ti,max-div:
>      $ref: /schemas/types.yaml#/definitions/uint32
>      description:
> @@ -116,20 +116,6 @@ properties:
>        valid divisor programming must be a power of two,
>        only valid if ti,dividers is not defined.
>  
> -  ti,autoidle-shift:
> -    $ref: /schemas/types.yaml#/definitions/uint32
> -    description:
> -      bit shift of the autoidle enable bit for the clock,
> -      see [1].
> -    maximum: 31
> -    default: 0
> -
now you make ti,autoidle-shift required. That makes so sense. A clock
does not necessarily support autoidle.

Regards,
Andreas

  parent reply	other threads:[~2025-04-05 19:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-04  1:44 [PATCH 0/4] dt-bindings: clock: ti: convert to yaml Sukrut Bellary
2025-04-04  1:44 ` [PATCH 1/4] dt-bindings: clock: ti: Convert " Sukrut Bellary
2025-04-04 10:44   ` Krzysztof Kozlowski
2025-04-05 19:55     ` Andreas Kemnade
2025-04-09  8:11       ` Sukrut Bellary
2025-04-09  7:46     ` Sukrut Bellary
2025-04-04 15:19   ` Rob Herring
2025-04-09  8:21     ` Sukrut Bellary
2025-04-04  1:44 ` [PATCH 2/4] " Sukrut Bellary
2025-04-04  5:51   ` kernel test robot
2025-04-04 10:46   ` Krzysztof Kozlowski
2025-04-09  8:23     ` Sukrut Bellary
2025-04-04 14:56   ` Rob Herring (Arm)
2025-04-09  8:35     ` Sukrut Bellary
2025-04-09  9:10   ` Andreas Kemnade
2025-04-10 17:49     ` Sukrut Bellary
2025-04-04  1:44 ` [PATCH 3/4] dt-bindings: clock: ti: Convert fixed-factor-clock " Sukrut Bellary
2025-04-04 19:40   ` Rob Herring
2025-04-09  8:38     ` Sukrut Bellary
2025-04-04  1:45 ` [PATCH 4/4] dt-bindings: clock: ti: add ti,autoidle.yaml reference Sukrut Bellary
2025-04-04 19:42   ` Rob Herring
2025-04-09  8:40     ` Sukrut Bellary
2025-04-05 19:49   ` Andreas Kemnade [this message]
2025-04-09  8:43     ` Sukrut Bellary

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=20250405214904.0b07b26f@akair \
    --to=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 \
    --cc=sboyd@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;
as well as URLs for NNTP newsgroup(s).