From: Viresh Kumar <viresh.kumar@linaro.org>
To: Hector Yuan <hector.yuan@mediatek.com>
Cc: Rob Herring <robh@kernel.org>,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, wsd_upstream@mediatek.com
Subject: Re: [PATCH v7 2/2] dt-bindings: cpufreq: add bindings for MediaTek cpufreq HW
Date: Fri, 25 Sep 2020 11:45:43 +0530 [thread overview]
Message-ID: <20200925061543.5hxs3ija2y53gzea@vireshk-i7> (raw)
In-Reply-To: <1601000847.21446.34.camel@mtkswgap22>
On 25-09-20, 10:27, Hector Yuan wrote:
> Hi, Viresh & Rob Sir:
>
> I will change frequency domain to below and define it in cpufreq_hw
> schema rather than cpu node.
>
> mediatek,freq-domain-0 = <&cpu0>, <&cpu1>;
I think it would be better to do it the standard way we have done it elsewhere.
i.e. follow Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.txt, that
is similar to what you did earlier.
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Hector Yuan <hector.yuan@mediatek.com>
Cc: Rob Herring <robh@kernel.org>,
wsd_upstream@mediatek.com, devicetree@vger.kernel.org,
linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 2/2] dt-bindings: cpufreq: add bindings for MediaTek cpufreq HW
Date: Fri, 25 Sep 2020 11:45:43 +0530 [thread overview]
Message-ID: <20200925061543.5hxs3ija2y53gzea@vireshk-i7> (raw)
In-Reply-To: <1601000847.21446.34.camel@mtkswgap22>
On 25-09-20, 10:27, Hector Yuan wrote:
> Hi, Viresh & Rob Sir:
>
> I will change frequency domain to below and define it in cpufreq_hw
> schema rather than cpu node.
>
> mediatek,freq-domain-0 = <&cpu0>, <&cpu1>;
I think it would be better to do it the standard way we have done it elsewhere.
i.e. follow Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.txt, that
is similar to what you did earlier.
--
viresh
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Hector Yuan <hector.yuan@mediatek.com>
Cc: Rob Herring <robh@kernel.org>,
wsd_upstream@mediatek.com, devicetree@vger.kernel.org,
linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 2/2] dt-bindings: cpufreq: add bindings for MediaTek cpufreq HW
Date: Fri, 25 Sep 2020 11:45:43 +0530 [thread overview]
Message-ID: <20200925061543.5hxs3ija2y53gzea@vireshk-i7> (raw)
In-Reply-To: <1601000847.21446.34.camel@mtkswgap22>
On 25-09-20, 10:27, Hector Yuan wrote:
> Hi, Viresh & Rob Sir:
>
> I will change frequency domain to below and define it in cpufreq_hw
> schema rather than cpu node.
>
> mediatek,freq-domain-0 = <&cpu0>, <&cpu1>;
I think it would be better to do it the standard way we have done it elsewhere.
i.e. follow Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.txt, that
is similar to what you did earlier.
--
viresh
_______________________________________________
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:[~2020-09-25 6:15 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 4:31 [PATCH v7] cpufreq: mediatek-hw: Add support for Mediatek cpufreq HW driver Hector Yuan
2020-09-10 4:31 ` Hector Yuan
2020-09-10 4:31 ` Hector Yuan
2020-09-10 4:31 ` [PATCH v7 1/2] " Hector Yuan
2020-09-10 4:31 ` Hector Yuan
2020-09-10 4:31 ` Hector Yuan
2020-09-10 4:31 ` [PATCH v7 2/2] dt-bindings: cpufreq: add bindings for MediaTek cpufreq HW Hector Yuan
2020-09-10 4:31 ` Hector Yuan
2020-09-10 4:31 ` Hector Yuan
2020-09-21 2:23 ` Hector Yuan
2020-09-21 2:23 ` Hector Yuan
2020-09-21 2:23 ` Hector Yuan
2020-09-22 20:28 ` Rob Herring
2020-09-22 20:28 ` Rob Herring
2020-09-22 20:28 ` Rob Herring
2020-09-23 13:10 ` Hector Yuan
2020-09-23 13:10 ` Hector Yuan
2020-09-23 13:10 ` Hector Yuan
2020-09-24 2:36 ` Hector Yuan
2020-09-24 2:36 ` Hector Yuan
2020-09-24 2:36 ` Hector Yuan
2020-09-25 2:27 ` Hector Yuan
2020-09-25 2:27 ` Hector Yuan
2020-09-25 2:27 ` Hector Yuan
2020-09-25 6:15 ` Viresh Kumar [this message]
2020-09-25 6:15 ` Viresh Kumar
2020-09-25 6:15 ` Viresh Kumar
2020-09-25 7:25 ` Hector Yuan
2020-09-25 7:25 ` Hector Yuan
2020-09-25 7:25 ` Hector Yuan
2020-10-05 2:29 ` Hector Yuan
2020-10-05 2:29 ` Hector Yuan
2020-10-05 2:29 ` Hector Yuan
2020-09-10 5:03 ` [PATCH v7] cpufreq: mediatek-hw: Add support for Mediatek cpufreq HW driver Viresh Kumar
2020-09-10 5:03 ` Viresh Kumar
2020-09-10 5:03 ` Viresh Kumar
2020-09-10 5:30 ` Hector Yuan
2020-09-10 5:30 ` Hector Yuan
2020-09-10 5:30 ` Hector Yuan
2020-09-10 5:34 ` Viresh Kumar
2020-09-10 5:34 ` Viresh Kumar
2020-09-10 5:34 ` Viresh Kumar
2020-09-16 11:39 ` Hector Yuan
2020-09-16 11:39 ` Hector Yuan
2020-09-16 11:39 ` Hector Yuan
2020-09-17 2:31 ` Hector Yuan
2020-09-17 2:31 ` Hector Yuan
2020-09-17 2:31 ` Hector Yuan
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=20200925061543.5hxs3ija2y53gzea@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=hector.yuan@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=robh@kernel.org \
--cc=wsd_upstream@mediatek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.