From: Wang Honghui <honghui.wang@ucas.com.cn>
To: Sudeep Holla <sudeep.holla@arm.com>,
Cristian Marussi <cristian.marussi@arm.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] clk-scpi: Modify to recall scpi_clocks_probe
Date: Fri, 25 Nov 2022 10:35:41 +0800 [thread overview]
Message-ID: <950BEC68ABB5129B+Y4Ap/WUNrJ2BTmYD@TP-P15V.lan> (raw)
Modify to recall scpi_clocks_probe
and add to support Phytium FT2000/4 CPUs
Signed-off-by: Wang Honghui <honghui.wang@ucas.com.cn>
---
drivers/clk/clk-scpi.c | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/drivers/clk/clk-scpi.c b/drivers/clk/clk-scpi.c
index a39af7616b13..fbc624c5a94a 100644
--- a/drivers/clk/clk-scpi.c
+++ b/drivers/clk/clk-scpi.c
@@ -268,8 +268,10 @@ static int scpi_clocks_probe(struct platform_device *pdev)
struct device_node *child, *np = dev->of_node;
const struct of_device_id *match;
+ /* Wang Honghui modified, the func will not be recalled
+ * if return -EIO, but will if return -EPROBE_DEFER */
if (!get_scpi_ops())
- return -ENXIO;
+ return -EPROBE_DEFER;
for_each_available_child_of_node(np, child) {
match = of_match_node(scpi_clk_match, child);
@@ -299,10 +301,18 @@ static const struct of_device_id scpi_clocks_ids[] = {
};
MODULE_DEVICE_TABLE(of, scpi_clocks_ids);
+/* Wang Honghui add to support Phytium FT2000/4 CPUs */
+static const struct acpi_device_id scpi_cpufreq_acpi_match[] = {
+ { .id = "PHYT8001" },
+ { }
+};
+MODULE_DEVICE_TABLE(acpi, scpi_clock_acpi_match);
+
static struct platform_driver scpi_clocks_driver = {
.driver = {
.name = "scpi_clocks",
.of_match_table = scpi_clocks_ids,
+ .acpi_match_table = scpi_cpufreq_acpi_match,
},
.probe = scpi_clocks_probe,
.remove = scpi_clocks_remove,
--
2.34.1
next reply other threads:[~2022-11-25 2:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 2:35 Wang Honghui [this message]
2022-11-25 9:45 ` Sudeep Holla
2022-11-25 18:37 ` kernel test robot
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=950BEC68ABB5129B+Y4Ap/WUNrJ2BTmYD@TP-P15V.lan \
--to=honghui.wang@ucas.com.cn \
--cc=cristian.marussi@arm.com \
--cc=jassisinghbrar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudeep.holla@arm.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 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®