public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Vibhore Vardhan <vibhore@ti.com>
To: <rafael@kernel.org>, <viresh.kumar@linaro.org>
Cc: <linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<vigneshr@ti.com>, <d-gole@ti.com>,
	Vibhore Vardhan <vibhore@ti.com>
Subject: [PATCH 2/2] cpufreq: dt-platdev: Blacklist ti,am62a7 SoC
Date: Fri, 26 May 2023 09:43:54 -0500	[thread overview]
Message-ID: <20230526144354.38478-3-vibhore@ti.com> (raw)
In-Reply-To: <20230526144354.38478-1-vibhore@ti.com>

Add ti,am62a7 SoC to the blacklist as the ti-cpufreq driver will handle
creating the cpufreq-dt platform device after it completes so it is not
created twice.

Based on AM625 CPUFreq patch series by Dave Gerlach.

Signed-off-by: Vibhore Vardhan <vibhore@ti.com>
---
 drivers/cpufreq/cpufreq-dt-platdev.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c
index 338cf6cc6596..9368911ce20b 100644
--- a/drivers/cpufreq/cpufreq-dt-platdev.c
+++ b/drivers/cpufreq/cpufreq-dt-platdev.c
@@ -165,6 +165,7 @@ static const struct of_device_id blocklist[] __initconst = {
 	{ .compatible = "ti,dra7", },
 	{ .compatible = "ti,omap3", },
 	{ .compatible = "ti,am625", },
+	{ .compatible = "ti,am62a7", },
 
 	{ .compatible = "qcom,ipq8064", },
 	{ .compatible = "qcom,apq8064", },
-- 
2.34.1


  parent reply	other threads:[~2023-05-26 14:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-26 14:43 [PATCH 0/2] cpufreq: ti-cpufreq: Enable AM62A7 CPUFreq Vibhore Vardhan
2023-05-26 14:43 ` [PATCH 1/2] cpufreq: ti-cpufreq: Add support for AM62A7 Vibhore Vardhan
2023-05-26 14:43 ` Vibhore Vardhan [this message]
2023-05-26 15:49 ` [PATCH 0/2] cpufreq: ti-cpufreq: Enable AM62A7 CPUFreq Dhruva Gole
2023-05-29  5:04 ` Viresh Kumar

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=20230526144354.38478-3-vibhore@ti.com \
    --to=vibhore@ti.com \
    --cc=d-gole@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=vigneshr@ti.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox