Devicetree
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH] dt-bindings: cpufreq: remove stale arm_big_little_dt entry
Date: Thu, 8 Nov 2018 10:15:41 +0530	[thread overview]
Message-ID: <20181108044541.vxry3vgbtconb3rb@vireshk-i7> (raw)
In-Reply-To: <20181107174058.4131-1-sudeep.holla@arm.com>

On 07-11-18, 17:40, Sudeep Holla wrote:
> Most of the ARM platforms used v2 OPP bindings to support big-little
> configurations. This arm_big_little_dt binding is incomplete and was
> never used.
> 
> Commit f174e49e4906 ("cpufreq: remove unused arm_big_little_dt driver")
> removes the driver supporting this binding. However the binding was left
> unnoticed, so let's get rid of it now.
> 
> Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
> Cc: Viresh Kumar <viresh.kumar@linaro.org>
> Cc: Rob Herring <robh+dt@kernel.org>
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> ---
>  .../bindings/cpufreq/arm_big_little_dt.txt    | 65 -------------------
>  1 file changed, 65 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/cpufreq/arm_big_little_dt.txt
> 
> Hi,
> 
> For some reason, I didn't expect the driver to have an entry in the
> DT bindings and didn't look at it before. While I was searching references
> to big-little that can be removed, I spotted this. Sorry for that.
> 
> Regards,
> Sudeep
> 
> diff --git a/Documentation/devicetree/bindings/cpufreq/arm_big_little_dt.txt b/Documentation/devicetree/bindings/cpufreq/arm_big_little_dt.txt
> deleted file mode 100644
> index 2aa06ac0fac5..000000000000
> --- a/Documentation/devicetree/bindings/cpufreq/arm_big_little_dt.txt
> +++ /dev/null
> @@ -1,65 +0,0 @@
> -Generic ARM big LITTLE cpufreq driver's DT glue
> ------------------------------------------------
> -
> -This is DT specific glue layer for generic cpufreq driver for big LITTLE
> -systems.
> -
> -Both required and optional properties listed below must be defined
> -under node /cpus/cpu@x. Where x is the first cpu inside a cluster.
> -
> -FIXME: Cpus should boot in the order specified in DT and all cpus for a cluster
> -must be present contiguously. Generic DT driver will check only node 'x' for
> -cpu:x.
> -
> -Required properties:
> -- operating-points: Refer to Documentation/devicetree/bindings/opp/opp.txt
> -  for details
> -
> -Optional properties:
> -- clock-latency: Specify the possible maximum transition latency for clock,
> -  in unit of nanoseconds.
> -
> -Examples:
> -
> -cpus {
> -	#address-cells = <1>;
> -	#size-cells = <0>;
> -
> -	cpu@0 {
> -		compatible = "arm,cortex-a15";
> -		reg = <0>;
> -		next-level-cache = <&L2>;
> -		operating-points = <
> -			/* kHz    uV */
> -			792000  1100000
> -			396000  950000
> -			198000  850000
> -		>;
> -		clock-latency = <61036>; /* two CLK32 periods */
> -	};
> -
> -	cpu@1 {
> -		compatible = "arm,cortex-a15";
> -		reg = <1>;
> -		next-level-cache = <&L2>;
> -	};
> -
> -	cpu@100 {
> -		compatible = "arm,cortex-a7";
> -		reg = <100>;
> -		next-level-cache = <&L2>;
> -		operating-points = <
> -			/* kHz    uV */
> -			792000  950000
> -			396000  750000
> -			198000  450000
> -		>;
> -		clock-latency = <61036>; /* two CLK32 periods */
> -	};
> -
> -	cpu@101 {
> -		compatible = "arm,cortex-a7";
> -		reg = <101>;
> -		next-level-cache = <&L2>;
> -	};
> -};

Acked-by: Viresh Kumar <viresh.kumar@linaro.org>

-- 
viresh

      reply	other threads:[~2018-11-08  4:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07 17:40 [PATCH] dt-bindings: cpufreq: remove stale arm_big_little_dt entry Sudeep Holla
2018-11-08  4:45 ` Viresh Kumar [this message]

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=20181108044541.vxry3vgbtconb3rb@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=robh+dt@kernel.org \
    --cc=sudeep.holla@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