From: Viresh Kumar <viresh.kumar@linaro.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Hector Yuan <hector.yuan@mediatek.com>,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
wsd_upstream@mediatek.com
Subject: Re: [PATCH v12 1/2] cpufreq: mediatek-hw: Add support for CPUFREQ HW
Date: Tue, 29 Jun 2021 08:17:19 +0530 [thread overview]
Message-ID: <20210629024719.nmcygaigtx5wn7g5@vireshk-i7> (raw)
In-Reply-To: <20210628090956.uwkrozdqvawsm3xp@bogus>
On 28-06-21, 10:09, Sudeep Holla wrote:
> Probably in driver/cpufreq or some related headers if it needs to access
> related_cpus and is more cpufreq related in that way ?
It just needs to set a mask, so doesn't really depend on cpufreq. I
was wondering if drivers/opp/of.c may be used for this, and I am not
sure.
> Orthogonal to that, I prefer to make the generic function take list_name
> and cells_name as generic. I see we can reuse that qcom-cpufreq-hw.c
> with "qcom,freq-domain" and "#freq-domain-cells".
Yes.
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Hector Yuan <hector.yuan@mediatek.com>,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
wsd_upstream@mediatek.com
Subject: Re: [PATCH v12 1/2] cpufreq: mediatek-hw: Add support for CPUFREQ HW
Date: Tue, 29 Jun 2021 08:17:19 +0530 [thread overview]
Message-ID: <20210629024719.nmcygaigtx5wn7g5@vireshk-i7> (raw)
In-Reply-To: <20210628090956.uwkrozdqvawsm3xp@bogus>
On 28-06-21, 10:09, Sudeep Holla wrote:
> Probably in driver/cpufreq or some related headers if it needs to access
> related_cpus and is more cpufreq related in that way ?
It just needs to set a mask, so doesn't really depend on cpufreq. I
was wondering if drivers/opp/of.c may be used for this, and I am not
sure.
> Orthogonal to that, I prefer to make the generic function take list_name
> and cells_name as generic. I see we can reuse that qcom-cpufreq-hw.c
> with "qcom,freq-domain" and "#freq-domain-cells".
Yes.
--
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: Sudeep Holla <sudeep.holla@arm.com>
Cc: Hector Yuan <hector.yuan@mediatek.com>,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
wsd_upstream@mediatek.com
Subject: Re: [PATCH v12 1/2] cpufreq: mediatek-hw: Add support for CPUFREQ HW
Date: Tue, 29 Jun 2021 08:17:19 +0530 [thread overview]
Message-ID: <20210629024719.nmcygaigtx5wn7g5@vireshk-i7> (raw)
In-Reply-To: <20210628090956.uwkrozdqvawsm3xp@bogus>
On 28-06-21, 10:09, Sudeep Holla wrote:
> Probably in driver/cpufreq or some related headers if it needs to access
> related_cpus and is more cpufreq related in that way ?
It just needs to set a mask, so doesn't really depend on cpufreq. I
was wondering if drivers/opp/of.c may be used for this, and I am not
sure.
> Orthogonal to that, I prefer to make the generic function take list_name
> and cells_name as generic. I see we can reuse that qcom-cpufreq-hw.c
> with "qcom,freq-domain" and "#freq-domain-cells".
Yes.
--
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:[~2021-06-29 2:47 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-29 16:52 [PATCH v12] cpufreq: mediatek-hw: Add support for Mediatek cpufreq HW driver Hector Yuan
2021-05-29 16:52 ` Hector Yuan
2021-05-29 16:52 ` Hector Yuan
2021-05-29 16:52 ` [PATCH v12 1/2] cpufreq: mediatek-hw: Add support for CPUFREQ HW Hector Yuan
2021-05-29 16:52 ` Hector Yuan
2021-05-29 16:52 ` Hector Yuan
2021-06-14 10:40 ` Viresh Kumar
2021-06-14 10:40 ` Viresh Kumar
2021-06-14 10:40 ` Viresh Kumar
[not found] ` <1624781848.1958.16.camel@mtkswgap22>
2021-06-28 7:26 ` Viresh Kumar
2021-06-28 7:26 ` Viresh Kumar
2021-06-28 7:26 ` Viresh Kumar
2021-06-28 9:09 ` Sudeep Holla
2021-06-28 9:09 ` Sudeep Holla
2021-06-28 9:09 ` Sudeep Holla
2021-06-29 2:47 ` Viresh Kumar [this message]
2021-06-29 2:47 ` Viresh Kumar
2021-06-29 2:47 ` Viresh Kumar
2021-06-29 9:02 ` Sudeep Holla
2021-06-29 9:02 ` Sudeep Holla
2021-06-29 9:02 ` Sudeep Holla
2021-06-29 9:05 ` Viresh Kumar
2021-06-29 9:05 ` Viresh Kumar
2021-06-29 9:05 ` Viresh Kumar
[not found] ` <1625418089.1958.48.camel@mtkswgap22>
2021-07-05 4:32 ` Viresh Kumar
2021-07-05 4:32 ` Viresh Kumar
2021-07-05 4:32 ` Viresh Kumar
2021-05-29 16:52 ` [PATCH v12 2/2] dt-bindings: cpufreq: add bindings for MediaTek cpufreq HW Hector Yuan
2021-05-29 16:52 ` Hector Yuan
2021-05-29 16:52 ` Hector Yuan
2021-06-02 16:58 ` Rob Herring
2021-06-02 16:58 ` Rob Herring
2021-06-02 16:58 ` Rob Herring
2021-06-27 7:56 ` Hector Yuan
2021-06-27 7:56 ` Hector Yuan
2021-06-27 7:56 ` 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=20210629024719.nmcygaigtx5wn7g5@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=matthias.bgg@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=sudeep.holla@arm.com \
--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.