From: Sudeep Holla <sudeep.holla@arm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: "Edwin Chiu 邱垂峰" <edwin.chiu@sunplus.com>,
"Edwin Chiu" <edwinchiu0505tw@gmail.com>,
"Sudeep Holla" <sudeep.holla@arm.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rafael@kernel.org" <rafael@kernel.org>,
"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v5] cpuidle: sunplus: Create cpuidle driver for sunplus sp7021
Date: Thu, 3 Mar 2022 10:02:40 +0000 [thread overview]
Message-ID: <YiCSQCG4NkepeZKs@bogus> (raw)
In-Reply-To: <fd39f73e-8317-38c4-6002-8defd784caec@kernel.org>
On Thu, Mar 03, 2022 at 10:34:31AM +0100, Krzysztof Kozlowski wrote:
> On 03/03/2022 10:01, Edwin Chiu 邱垂峰 wrote:
> >
> >
> >> -----Original Message-----
> >> From: Krzysztof Kozlowski <krzk@kernel.org>
> >> Sent: Tuesday, March 1, 2022 7:34 PM
> >> To: Edwin Chiu 邱垂峰 <edwin.chiu@sunplus.com>; Edwin Chiu <edwinchiu0505tw@gmail.com>;
> >> robh+dt@kernel.org; devicetree@vger.kernel.org; linux-kernel@vger.kernel.org; rafael@kernel.org;
> >> daniel.lezcano@linaro.org; linux-pm@vger.kernel.org
> >> Subject: Re: [PATCH v5] cpuidle: sunplus: Create cpuidle driver for sunplus sp7021
> >>
> >> On 01/03/2022 10:30, Edwin Chiu 邱垂峰 wrote:
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: Krzysztof Kozlowski <krzk@kernel.org>
> >>>> Sent: Tuesday, February 22, 2022 12:48 AM
> >>>> To: Edwin Chiu <edwinchiu0505tw@gmail.com>; Edwin Chiu 邱垂峰
> >>>> <edwin.chiu@sunplus.com>;
> >>>> robh+dt@kernel.org; devicetree@vger.kernel.org;
> >>>> robh+linux-kernel@vger.kernel.org; rafael@kernel.org;
> >>>> daniel.lezcano@linaro.org; linux-pm@vger.kernel.org
> >>>> Subject: Re: [PATCH v5] cpuidle: sunplus: Create cpuidle driver for
> >>>> sunplus sp7021
> >>>>
> >>>> On 21/02/2022 08:26, Edwin Chiu wrote:
> >>>>> Create cpuidle driver for sunplus sp7021 chip
> >>>>>
> >>>>> Signed-off-by: Edwin Chiu <edwinchiu0505tw@gmail.com>
> >>>>> ---
> >>>>> Changes in v3
> >>>>> - Rearrangement #include sequence
> >>>>> - Change remark style to /*~*/
> >>>>> - Align author email address to same as sob
> >>>>> - Optimal code
> >>>>> Changes in v4
> >>>>> - According Rob Herringrobh's comment
> >>>>> There is no need for this binding.
> >>>>> Just wanting a different driver is not a reason
> >>>>> for a duplicate schema.
> >>>>> So remove yaml file and submit driver again.
> >>>>> Changes in v5
> >>>>> - According Krzysztof's comment
> >>>>> You either use appropriate compatible in DT
> >>>>> or add your compatible to cpuidle-arm.
> >>>>> Even if this did not work, then the solution is to
> >>>>> use common parts, not to duplicate entire driver.
> >>>>> According Sudeep's comment
> >>>>> In short NACK for any dedicated driver for this platform,
> >>>>> use the generic cpuidle-arm driver with appropriate platform hooks
> >>>>> Create cpuidle-sunplus.c in arch/arm/mach-sunplus/
> >>>>> for hook generic cpuidle-arm driver
> >>>>>
> >>>>> MAINTAINERS | 6 ++
> >>>>> arch/arm/mach-sunplus/cpuidle-sunplus.c | 88 +++++++++++++++++
> >>>>> include/linux/platform_data/cpuidle-sunplus.h | 12 ++++
> >>>>> 3 files changed, 106 insertions(+)
> >>>>> create mode 100644 arch/arm/mach-sunplus/cpuidle-sunplus.c
> >>>>> create mode 100644 include/linux/platform_data/cpuidle-sunplus.h
> >>>>>
> >>>>> diff --git a/MAINTAINERS b/MAINTAINERS index e0dca8f..5c96428 100644
> >>>>> --- a/MAINTAINERS
> >>>>> +++ b/MAINTAINERS
> >>>>> @@ -18252,6 +18252,12 @@ L: netdev@vger.kernel.org
> >>>>> S: Maintained
> >>>>> F: drivers/net/ethernet/dlink/sundance.c
> >>>>>
> >>>>> +SUNPLUS CPUIDLE DRIVER
> >>>>> +M: Edwin Chiu <edwinchiu0505tw@gmail.com>
> >>>>> +S: Maintained
> >>>>> +F: arch/arm/mach-sunplus/cpuidle-sunplus.c
> >>>>> +F: include/linux/platform_data/cpuidle-sunplus.h
> >>>>> +
> >>>>> SUPERH
> >>>>> M: Yoshinori Sato <ysato@users.sourceforge.jp>
> >>>>> M: Rich Felker <dalias@libc.org>
> >>>>> diff --git a/arch/arm/mach-sunplus/cpuidle-sunplus.c
> >>>>> b/arch/arm/mach-sunplus/cpuidle-sunplus.c
> >>>>> new file mode 100644
> >>>>> index 0000000..e9d9738
> >>>>> --- /dev/null
> >>>>> +++ b/arch/arm/mach-sunplus/cpuidle-sunplus.c
> >>>>> @@ -0,0 +1,88 @@
> >>>>> +// SPDX-License-Identifier: GPL-2.0-only
> >>>>> +/*
> >>>>> + * SP7021 cpu idle Driver.
> >>>>> + * Copyright (C) Sunplus Tech / Tibbo Tech.
> >>>>> + */
> >>>>> +#define pr_fmt(fmt) "CPUidle arm: " fmt
> >>>>> +
> >>>>> +#include <linux/cpuidle.h>
> >>>>> +#include <linux/of_device.h>
> >>>>> +#include <linux/platform_data/cpuidle-sunplus.h>
> >>>>> +
> >>>>> +#include <asm/cpuidle.h>
> >>>>> +
> >>>>> +typedef int (*idle_fn)(void);
> >>>>> +
> >>>>> +static DEFINE_PER_CPU(idle_fn*, sp7021_idle_ops);
> >>>>> +
> >>>>> +static int sp7021_cpuidle_enter(unsigned long index) {
> >>>>> + return __this_cpu_read(sp7021_idle_ops)[index]();
> >>>>> +}
> >>>>> +static int sp7021_cpu_spc(void)
> >>>>> +{
> >>>>> + cpu_v7_do_idle(); /* idle to WFI */
> >>>>> + return 0;
> >>>>> +}
> >>>>> +static const struct of_device_id sp7021_idle_state_match[] = {
> >>>>> + { .compatible = "arm,idle-state", .data = sp7021_cpu_spc },
> >>>>> + { },
> >>>>> +};
> >>>>
> >>>> This is confusing. You want to have two drivers to bind to the same
> >>>> compatible? As I wrote in the previous messages, you should simply use arm,idle-state just like few
> >> other architectures.
> >>>>
> >>>>
> >>>> Best regards,
> >>>> Krzysztof
> >>>
> >>>
> >>> The patch v5 implemented according your comment.
> >>> Used common part of arm,idle-state.
> >>> Create new enable-method for cpuidle.ops function.
> >>> It only have arm cpuidle driver exist now, no two drivers to bind to the same compatible.
> >>>
> >>> What do you mean " simply use arm,idle-state just like few other architectures "?
> >>>
> >>
> >> I mean, do it similarly (by using arm,idle-state and other related
> >> properties) to for example ti,am4372/ti,am3352.
> >>
> >> Best regards,
> >> Krzysztof
> >
> >
> > The am3352 cpuidle code structure is very similar to ours.
> > Used enable-method = "ti,am3352" and compatible = "arm,idle-state" in am33xx.dtsi
> > Used CPUIDLE_METHOD_OF_DECLARE(pm33xx_idle, "ti,am3352", &amx3_cpuidle_ops) in pm33xx-core.c
> >
> > The difference are
> > am3352
> > amx3_idle_init(~) assign idle_states[i].wfi_flags = states[i].wfi_flags;
> > amx3_idle_enter(~) call idle_fn(idle_state->wfi_flags)
> >
> > sunplus-sp7021
> > sp7021_cpuidle_init(~) assign fns[i] = idle_fns[i];
> > sp7021_cpuidle_enter(~) call __this_cpu_read(sp7021_idle_ops)[index]();
> >
> > I don't think am3352 cpuidle code architecture simpler than ours.
> > The idle_fn function need more complex method to be assign.
> > How do you think?
>
> You duplicated a driver, entire pieces of code. This is not acceptable.
> Therefore it does not really make sense to discuss whether duplicated
> solution seems simpler or not... We won't accept duplicated code.
> Especially for WFI-only driver.
>
+1 for above comment.
In addition, the reference platform am33xx* doesn't seem to support hotplug
(may be I am missing to see but quick grep gave no results) and their idle
is definitely not just WFI. So what I asked is that please document the
chosen "sunplus,sc-smp" as bot cpu idle and hotplug methods and when you
support non WFI states, we can revisit this. Also you must stick to this
hotplug method whenever you decided to support it.
--
Regards,
Sudeep
next prev parent reply other threads:[~2022-03-03 10:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 7:26 [PATCH v5] Add cpuidle driver for Sunplus SP7021 Edwin Chiu
2022-02-21 7:26 ` [PATCH v5] cpuidle: sunplus: Create cpuidle driver for sunplus sp7021 Edwin Chiu
2022-02-21 10:51 ` Sudeep Holla
2022-03-01 9:18 ` Edwin Chiu 邱垂峰
2022-03-01 12:23 ` Sudeep Holla
2022-02-21 16:47 ` Krzysztof Kozlowski
2022-03-01 9:30 ` Edwin Chiu 邱垂峰
2022-03-01 11:33 ` Krzysztof Kozlowski
2022-03-03 9:01 ` Edwin Chiu 邱垂峰
2022-03-03 9:34 ` Krzysztof Kozlowski
2022-03-03 10:02 ` Sudeep Holla [this message]
2022-03-04 11:24 ` Edwin Chiu 邱垂峰
2022-03-04 14:37 ` Sudeep Holla
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=YiCSQCG4NkepeZKs@bogus \
--to=sudeep.holla@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=edwin.chiu@sunplus.com \
--cc=edwinchiu0505tw@gmail.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).