From: sricharan@codeaurora.org
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: mark.rutland@arm.com, robh@kernel.org, linux@arm.linux.org.uk,
ctatlor97@gmail.com, rjw@rjwysocki.net, viresh.kumar@linaro.org,
mturquette@baylibre.com, linux-pm@vger.kernel.org,
sboyd@codeaurora.org, linux@armlinux.org.uk,
thierry.escande@linaro.org, linux-kernel@vger.kernel.org,
david.brown@linaro.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, andy.gross@linaro.org,
linux-soc@vger.kernel.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v10 13/14] cpufreq: Add module to register cpufreq on Krait CPUs
Date: Wed, 20 Jun 2018 14:38:58 +0530 [thread overview]
Message-ID: <4a15ab80f732ae22f12a1351550be6dc@codeaurora.org> (raw)
In-Reply-To: <f195e30e-bef3-9352-9584-fec35631ec5e@arm.com>
Hi Sudeep,
>>
>> Register a cpufreq-generic device whenever we detect that a
>> "qcom,krait" compatible CPU is present in DT.
>>
>
> Just curious to know how different is this from qcom kryo driver
> that was added recently. IIRC even that gets the speedbin from nvmem.
> Can they be merged ? I don't see need to have different driver for
> Krait
> and Kryo CPUs when the code is not even remotely related to CPU type.
>
> Sorry if I have missed anything from previous versions, I just happen
> to open and looked at this series first time today.
Correct, having these two merged was pointed out earlier as well by
Viresh.
Now that kryo is merged, i will check once and see if they can be
nicely
merged.
Regards,
Sricharan
WARNING: multiple messages have this Message-ID (diff)
From: sricharan@codeaurora.org (sricharan at codeaurora.org)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v10 13/14] cpufreq: Add module to register cpufreq on Krait CPUs
Date: Wed, 20 Jun 2018 14:38:58 +0530 [thread overview]
Message-ID: <4a15ab80f732ae22f12a1351550be6dc@codeaurora.org> (raw)
In-Reply-To: <f195e30e-bef3-9352-9584-fec35631ec5e@arm.com>
Hi Sudeep,
>>
>> Register a cpufreq-generic device whenever we detect that a
>> "qcom,krait" compatible CPU is present in DT.
>>
>
> Just curious to know how different is this from qcom kryo driver
> that was added recently. IIRC even that gets the speedbin from nvmem.
> Can they be merged ? I don't see need to have different driver for
> Krait
> and Kryo CPUs when the code is not even remotely related to CPU type.
>
> Sorry if I have missed anything from previous versions, I just happen
> to open and looked at this series first time today.
Correct, having these two merged was pointed out earlier as well by
Viresh.
Now that kryo is merged, i will check once and see if they can be
nicely
merged.
Regards,
Sricharan
next prev parent reply other threads:[~2018-06-20 9:08 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 13:45 [PATCH v10 00/14] Krait clocks + Krait CPUfreq Sricharan R
2018-06-19 13:45 ` Sricharan R
2018-06-19 13:45 ` [PATCH v10 01/14] ARM: Add Krait L2 register accessor functions Sricharan R
2018-06-19 13:45 ` Sricharan R
2018-06-19 13:45 ` [PATCH v10 02/14] clk: qcom: Add support for High-Frequency PLLs (HFPLLs) Sricharan R
2018-06-19 13:45 ` Sricharan R
2018-06-19 13:45 ` [PATCH v10 03/14] clk: qcom: Add HFPLL driver Sricharan R
2018-06-19 13:45 ` Sricharan R
2018-06-19 13:45 ` [PATCH v10 04/14] dt-bindings: clock: Document qcom,hfpll Sricharan R
2018-06-19 13:45 ` Sricharan R
2018-06-19 13:45 ` [PATCH v10 05/14] clk: qcom: Add MSM8960/APQ8064's HFPLLs Sricharan R
2018-06-19 13:45 ` Sricharan R
2018-06-19 13:45 ` [PATCH v10 06/14] clk: qcom: Add IPQ806X's HFPLLs Sricharan R
2018-06-19 13:45 ` Sricharan R
2018-06-19 13:45 ` [PATCH v10 07/14] clk: qcom: Add support for Krait clocks Sricharan R
2018-06-19 13:45 ` Sricharan R
2018-06-19 13:45 ` [PATCH v10 08/14] clk: qcom: Add KPSS ACC/GCC driver Sricharan R
2018-06-19 13:45 ` Sricharan R
2018-06-19 13:45 ` [PATCH v10 09/14] dt-bindings: arm: Document qcom,kpss-gcc Sricharan R
2018-06-19 13:45 ` Sricharan R
2018-06-19 13:45 ` [PATCH v10 10/14] clk: qcom: Add Krait clock controller driver Sricharan R
2018-06-19 13:45 ` Sricharan R
2018-06-19 13:45 ` [PATCH v10 11/14] dt-bindings: clock: Document qcom,krait-cc Sricharan R
2018-06-19 13:45 ` Sricharan R
2018-06-19 13:45 ` [PATCH v10 12/14] clk: qcom: Add safe switch hook for krait mux clocks Sricharan R
2018-06-19 13:45 ` Sricharan R
2018-06-19 13:45 ` [PATCH v10 13/14] cpufreq: Add module to register cpufreq on Krait CPUs Sricharan R
2018-06-19 13:45 ` Sricharan R
2018-06-19 13:56 ` Sudeep Holla
2018-06-19 13:56 ` Sudeep Holla
2018-06-19 14:49 ` Craig Tatlor
2018-06-20 9:08 ` sricharan [this message]
2018-06-20 9:08 ` sricharan at codeaurora.org
2018-06-19 15:29 ` Craig Tatlor
2018-06-19 15:29 ` Craig Tatlor
2018-06-20 8:48 ` sricharan
2018-06-20 8:48 ` sricharan at codeaurora.org
2018-06-19 13:45 ` [PATCH v10 14/14] dt-bindings: cpufreq: Document operating-points-v2-krait-cpu Sricharan R
2018-06-19 13:45 ` Sricharan R
2018-06-27 9:31 ` [PATCH v10 00/14] Krait clocks + Krait CPUfreq Thierry Escande
2018-06-27 9:31 ` Thierry Escande
2018-06-28 4:29 ` Sricharan R
2018-06-28 4:29 ` Sricharan R
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=4a15ab80f732ae22f12a1351550be6dc@codeaurora.org \
--to=sricharan@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=ctatlor97@gmail.com \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=rjw@rjwysocki.net \
--cc=robh@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=sudeep.holla@arm.com \
--cc=thierry.escande@linaro.org \
--cc=viresh.kumar@linaro.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 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.