From: Krzysztof Kozlowski <krzk@kernel.org>
To: Edwin Chiu <edwinchiu0505tw@gmail.com>,
edwin.chiu@sunplus.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
Date: Mon, 21 Feb 2022 17:47:46 +0100 [thread overview]
Message-ID: <394261d1-f1df-e80d-3591-10f2d649e731@kernel.org> (raw)
In-Reply-To: <1628e048220f066204b8ac27f3cedf7f3cc02963.1645427180.git.edwinchiu0505tw@gmail.com>
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
next prev parent reply other threads:[~2022-02-21 16:47 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 [this message]
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
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=394261d1-f1df-e80d-3591-10f2d649e731@kernel.org \
--to=krzk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=edwin.chiu@sunplus.com \
--cc=edwinchiu0505tw@gmail.com \
--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