mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alain Volmat <avolmat@me.com>
To: Patrice Chotard <patrice.chotard@st.com>,
	linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: avolmat@me.com
Subject: [PATCH 2/3] cpufreq: dt-platdev: Blacklist st,stih418 SoC
Date: Mon, 31 Aug 2020 08:10:12 +0200	[thread overview]
Message-ID: <20200831061013.4327-3-avolmat@me.com> (raw)
In-Reply-To: <20200831061013.4327-1-avolmat@me.com>

Add st,stih418 SoC in the blacklist since the cpufreq driver
for this platform is already registering the driver.

Signed-off-by: Alain Volmat <avolmat@me.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 7d01df7bfa6c..3776d960f405 100644
--- a/drivers/cpufreq/cpufreq-dt-platdev.c
+++ b/drivers/cpufreq/cpufreq-dt-platdev.c
@@ -137,6 +137,7 @@ static const struct of_device_id blacklist[] __initconst = {
 
 	{ .compatible = "st,stih407", },
 	{ .compatible = "st,stih410", },
+	{ .compatible = "st,stih418", },
 
 	{ .compatible = "sigma,tango4", },
 
-- 
2.17.1


  parent reply	other threads:[~2020-08-31  6:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31  6:10 [PATCH 0/3] Enable CPUFreq for STi stih418 SoC Alain Volmat
2020-08-31  6:10 ` [PATCH 1/3] cpufreq: sti-cpufreq: add stih418 support Alain Volmat
2020-08-31  6:10 ` Alain Volmat [this message]
2020-08-31  6:10 ` [PATCH 3/3] cpufreq: arm: Kconfig: add CPUFREQ_DT depend for STI CPUFREQ Alain Volmat
2020-09-03 10:43 ` [PATCH 0/3] Enable CPUFreq for STi stih418 SoC 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=20200831061013.4327-3-avolmat@me.com \
    --to=avolmat@me.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=patrice.chotard@st.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®