All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hector Yuan <hector.yuan@mediatek.com>
To: Rob Herring <robh@kernel.org>
Cc: <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>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: [PATCH v7 2/2] dt-bindings: cpufreq: add bindings for MediaTek cpufreq HW
Date: Mon, 5 Oct 2020 10:29:36 +0800	[thread overview]
Message-ID: <1601864976.21446.46.camel@mtkswgap22> (raw)
In-Reply-To: <1601018748.21446.43.camel@mtkswgap22>

On Fri, 2020-09-25 at 15:25 +0800, Hector Yuan wrote:
> Hi, Rob sir:
> 
> Yes, my patch follows
> Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.txt way to
> define frequency domain.
> Is it OK to you if I use the same way to do?
> And if there exist any schema problem, please kindly let me know how to
> fix it.
> 
> My patch reference
> Documentation/devicetree/bindings/thermal/thermal-cooling-devices.yaml
> to use the cpu node.
> https://elixir.bootlin.com/linux/v5.9-rc6/source/Documentation/devicetree/bindings/thermal/thermal-cooling-devices.yaml
> 
> Thanks a lot.
> 
Hi, Rob sir:

Sorry to bother you, may we know your comment for this.
Thanks so much. 

> On Fri, 2020-09-25 at 11:45 +0530, Viresh Kumar wrote:
> > 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.
> > 
> 


WARNING: multiple messages have this Message-ID (diff)
From: Hector Yuan <hector.yuan@mediatek.com>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, wsd_upstream@mediatek.com,
	linux-pm@vger.kernel.org, Viresh Kumar <viresh.kumar@linaro.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: Mon, 5 Oct 2020 10:29:36 +0800	[thread overview]
Message-ID: <1601864976.21446.46.camel@mtkswgap22> (raw)
In-Reply-To: <1601018748.21446.43.camel@mtkswgap22>

On Fri, 2020-09-25 at 15:25 +0800, Hector Yuan wrote:
> Hi, Rob sir:
> 
> Yes, my patch follows
> Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.txt way to
> define frequency domain.
> Is it OK to you if I use the same way to do?
> And if there exist any schema problem, please kindly let me know how to
> fix it.
> 
> My patch reference
> Documentation/devicetree/bindings/thermal/thermal-cooling-devices.yaml
> to use the cpu node.
> https://elixir.bootlin.com/linux/v5.9-rc6/source/Documentation/devicetree/bindings/thermal/thermal-cooling-devices.yaml
> 
> Thanks a lot.
> 
Hi, Rob sir:

Sorry to bother you, may we know your comment for this.
Thanks so much. 

> On Fri, 2020-09-25 at 11:45 +0530, Viresh Kumar wrote:
> > 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.
> > 
> 

_______________________________________________
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: Hector Yuan <hector.yuan@mediatek.com>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, wsd_upstream@mediatek.com,
	linux-pm@vger.kernel.org, Viresh Kumar <viresh.kumar@linaro.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: Mon, 5 Oct 2020 10:29:36 +0800	[thread overview]
Message-ID: <1601864976.21446.46.camel@mtkswgap22> (raw)
In-Reply-To: <1601018748.21446.43.camel@mtkswgap22>

On Fri, 2020-09-25 at 15:25 +0800, Hector Yuan wrote:
> Hi, Rob sir:
> 
> Yes, my patch follows
> Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.txt way to
> define frequency domain.
> Is it OK to you if I use the same way to do?
> And if there exist any schema problem, please kindly let me know how to
> fix it.
> 
> My patch reference
> Documentation/devicetree/bindings/thermal/thermal-cooling-devices.yaml
> to use the cpu node.
> https://elixir.bootlin.com/linux/v5.9-rc6/source/Documentation/devicetree/bindings/thermal/thermal-cooling-devices.yaml
> 
> Thanks a lot.
> 
Hi, Rob sir:

Sorry to bother you, may we know your comment for this.
Thanks so much. 

> On Fri, 2020-09-25 at 11:45 +0530, Viresh Kumar wrote:
> > 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.
> > 
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-10-05  2:29 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
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 [this message]
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=1601864976.21446.46.camel@mtkswgap22 \
    --to=hector.yuan@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --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=viresh.kumar@linaro.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.