devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Edwin Chiu <edwinchiu0505tw@gmail.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	rafael@kernel.org, daniel.lezcano@linaro.org,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bingings:arm:sunplus:add sp7021 compatible string to sunplus,idle-state.yaml
Date: Tue, 11 Jan 2022 19:39:30 -0600	[thread overview]
Message-ID: <Yd4xUscZwoRHiOzF@robh.at.kernel.org> (raw)
In-Reply-To: <317c55864546698b02c39b16b082812c2ac9400c.1641432983.git.edwinchiu0505tw@gmail.com>

On Thu, Jan 06, 2022 at 10:00:07AM +0800, Edwin Chiu wrote:
> Add the compatible string for cpuidle state on sp7021
> 
> Signed-off-by: Edwin Chiu <edwinchiu0505tw@gmail.com>
> ---
> Changes in v3
>  - Align email address of sob and sender
>  - Added sp7021 compatible string
> 
>  .../bindings/arm/sunplus/sunplus,idle-state.yaml   | 59 ++++++++++++++++++++++
>  MAINTAINERS                                        |  5 ++
>  2 files changed, 64 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/arm/sunplus/sunplus,idle-state.yaml
> 
> diff --git a/Documentation/devicetree/bindings/arm/sunplus/sunplus,idle-state.yaml b/Documentation/devicetree/bindings/arm/sunplus/sunplus,idle-state.yaml
> new file mode 100644
> index 0000000..64281ba
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/sunplus/sunplus,idle-state.yaml
> @@ -0,0 +1,59 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +# Copyright (C) Sunplus Co., Ltd. 2021
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/arm/sunplus/sunplus,idle-state.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Sunplus SOC cpuidle state
> +
> +maintainers:
> +  - Edwin Chiu<edwinchiu0505tw@gmail.com>
> +
> +description: |
> +  Sunplus SOC cpuidle state
> +
> +properties:
> +  compatible:
> +    oneOf:
> +      - items:
> +          - enum:
> +              - sunplus,sp7021-idle-state
> +
> +  entry-latency-us:
> +    description:
> +      Worst case latency in microseconds required to enter the idle state.
> +
> +  exit-latency-us:
> +    description:
> +      Worst case latency in microseconds required to exit the idle state.
> +      The exit-latency-us duration may be guaranteed only after
> +      entry-latency-us has passed.
> +
> +  min-residency-us:
> +    description:
> +      Minimum residency duration in microseconds, inclusive of preparation
> +      and entry, for this idle state to be considered worthwhile energy wise
> +      (refer to section 2 of this document for a complete description).
> +
> +required:
> +  - compatible
> +  - entry-latency-us
> +  - exit-latency-us
> +  - min-residency-us
> +
> +additionalProperties: true
> +
> +examples:
> +  - |
> +
> +    idle-state {
> +      CPU_IDLE: cpu_idle {
> +        compatible = "sunplus,sp7021-idle-state";
> +        entry-latency-us = <8000>;
> +        exit-latency-us = <700>;
> +        min-residency-us = <9000>;
> +      };
> +    };

Again, this is no different than the generic binding. There is no need 
for this binding. Just wanting a different driver is not a reason for a 
duplicate schema.

Rob

  reply	other threads:[~2022-01-12  1:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06  2:00 [PATCH v3 0/2] Add cpuidle driver for Sunplus SP7021 Edwin Chiu
2022-01-06  2:00 ` [PATCH v3 1/2] dt-bingings:arm:sunplus:add sp7021 compatible string to sunplus,idle-state.yaml Edwin Chiu
2022-01-12  1:39   ` Rob Herring [this message]
2022-01-06  2:00 ` [PATCH v3 2/2] cpuidle:sunplus:create cpuidle driver for sunplus sp7021 Edwin Chiu

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=Yd4xUscZwoRHiOzF@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=edwinchiu0505tw@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@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).