From: "Agrawal, Akshu" <aagrawal2@amd.com>
To: Stephen Boyd <sboyd@kernel.org>, akshu.agrawal@amd.com
Cc: Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] clk: x86: Support RV architecture
Date: Mon, 20 Jul 2020 10:29:36 +0530 [thread overview]
Message-ID: <c671c1a6-6d4c-f57d-7d60-d62ee84a56ea@amd.com> (raw)
In-Reply-To: <159486139638.1987609.10837351469119432355@swboyd.mtv.corp.google.com>
On 7/16/2020 6:33 AM, Stephen Boyd wrote:
> Quoting Akshu Agrawal (2020-07-12 17:59:52)
>> There is minor difference between previous family of SoC and
>> the current one. Which is the there is only 48Mh fixed clk.
>> There is no mux and no option to select another freq as there in previous.
>>
>> Signed-off-by: Akshu Agrawal <akshu.agrawal@amd.com>
>> ---
> I only see four out of five patches and there isn't a cover letter. I
> have no idea if I can apply this change or if you're expecting me to ack
> it. Please help make my life a little easier!
Numbering went wrong due to another unrelated patch.
Will send another with cover letter explaining the series.
>> drivers/clk/x86/clk-fch.c | 55 ++++++++++++++++++++++++++++-----------
>> 1 file changed, 40 insertions(+), 15 deletions(-)
>>
>> diff --git a/drivers/clk/x86/clk-fch.c b/drivers/clk/x86/clk-fch.c
>> index b252f0cf0628..a8aac71a3b65 100644
>> --- a/drivers/clk/x86/clk-fch.c
>> +++ b/drivers/clk/x86/clk-fch.c
>> @@ -61,9 +78,17 @@ static int fch_clk_probe(struct platform_device *pdev)
>> static int fch_clk_remove(struct platform_device *pdev)
>> {
>> int i;
>> + struct fch_clk_data *fch_data;
>> +
>> + fch_data = dev_get_platdata(&pdev->dev);
>>
>> - for (i = 0; i < ST_MAX_CLKS; i++)
>> - clk_hw_unregister(hws[i]);
>> + if (!fch_data->is_rv) {
>> + for (i = 0; i < ST_MAX_CLKS; i++)
>> + clk_hw_unregister(hws[i]);
>> + } else {
>> + for (i = 0; i < RV_MAX_CLKS; i++)
>> + clk_hw_unregister(hws[i]);
> Can ST_MAX_CLKS or RV_MAX_CLKS be a local variable and then the loop
> consolidated.
Yes, making the change in next series.
Thanks,
Akshu
prev parent reply other threads:[~2020-07-20 4:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 0:59 [PATCH 1/5] ACPI: APD: Change name from ST to FCH Akshu Agrawal
2020-07-13 0:59 ` [PATCH 2/5] clk: x86: " Akshu Agrawal
2020-07-16 0:42 ` Stephen Boyd
2020-07-20 4:59 ` Agrawal, Akshu
2020-07-21 8:04 ` Stephen Boyd
2020-07-13 0:59 ` [PATCH 3/5] ACPI: APD: Add a fmw property is_raven Akshu Agrawal
2020-07-13 0:59 ` [PATCH 4/5] clk: x86: Support RV architecture Akshu Agrawal
2020-07-16 1:03 ` Stephen Boyd
2020-07-20 4:59 ` Agrawal, Akshu [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=c671c1a6-6d4c-f57d-7d60-d62ee84a56ea@amd.com \
--to=aagrawal2@amd.com \
--cc=akshu.agrawal@amd.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®