From: Nishanth Menon <nm@ti.com>
To: Santosh Shilimkar <ssantosh@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Swapnil Jakhade <sjakhade@cadence.com>,
Jyri Sarha <jsarha@ti.com>, Yuti Amonkar <yamonkar@cadence.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Lokesh Vutla <lokeshvutla@ti.com>, Tero Kristo <t-kristo@ti.com>,
Sekhar Nori <nsekhar@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Nishanth Menon <nm@ti.com>
Subject: [PATCH] soc: ti: Kconfig: Drop ARM64 SoC specific configs
Date: Mon, 26 Oct 2020 12:06:24 -0500 [thread overview]
Message-ID: <20201026170624.24241-1-nm@ti.com> (raw)
With the integration of chip-id detection scheme in kernel[1], there
is no specific need to maintain multitudes of SoC specific config
options, discussed as per [2], we have deprecated the usage in other
places for v5.10-rc1. Drop the configuration for the follow on kernel.
[1] drivers/soc/ti/k3-socinfo.c commit 907a2b7e2fc7 ("soc: ti: add k3 platforms chipid module driver")
[2] https://lore.kernel.org/linux-arm-kernel/20200908112534.t5bgrjf7y3a6l2ss@akan/
Signed-off-by: Nishanth Menon <nm@ti.com>
---
drivers/soc/ti/Kconfig | 18 ------------------
1 file changed, 18 deletions(-)
diff --git a/drivers/soc/ti/Kconfig b/drivers/soc/ti/Kconfig
index f5b82ffa637b..7e2fb1c16af1 100644
--- a/drivers/soc/ti/Kconfig
+++ b/drivers/soc/ti/Kconfig
@@ -1,22 +1,4 @@
# SPDX-License-Identifier: GPL-2.0-only
-# 64-bit ARM SoCs from TI
-if ARM64
-
-if ARCH_K3
-
-config ARCH_K3_AM6_SOC
- bool "K3 AM6 SoC"
- help
- Enable support for TI's AM6 SoC Family support
-
-config ARCH_K3_J721E_SOC
- bool "K3 J721E SoC"
- help
- Enable support for TI's J721E SoC Family support
-
-endif
-
-endif
#
# TI SOC drivers
--
2.28.0
next reply other threads:[~2020-10-26 17:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 17:06 Nishanth Menon [this message]
2020-10-26 18:00 ` [PATCH] soc: ti: Kconfig: Drop ARM64 SoC specific configs Lokesh Vutla
2020-10-26 19:08 ` Nishanth Menon
2020-10-27 15:59 ` Lokesh Vutla
2020-10-27 16:23 ` Nishanth Menon
2020-11-12 21:56 ` Nishanth Menon
2020-11-12 21:59 ` santosh.shilimkar
2020-11-12 22:22 ` Nishanth Menon
2020-11-13 1:13 ` santosh.shilimkar
2020-11-13 2:47 ` Nishanth Menon
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=20201026170624.24241-1-nm@ti.com \
--to=nm@ti.com \
--cc=jsarha@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=sjakhade@cadence.com \
--cc=ssantosh@kernel.org \
--cc=t-kristo@ti.com \
--cc=tomi.valkeinen@ti.com \
--cc=yamonkar@cadence.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;
as well as URLs for NNTP newsgroup(s).