From: Judith Mendez <jm@ti.com>
To: Judith Mendez <jm@ti.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Ulf Hansson <ulf.hansson@linaro.org>, Nishanth Menon <nm@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>
Cc: <linux-mmc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, Andrew Davis <afd@ti.com>
Subject: [PATCH v2 0/2] Add support for AM62P SR1.2
Date: Thu, 7 Aug 2025 17:51:36 -0500 [thread overview]
Message-ID: <20250807225138.1228333-1-jm@ti.com> (raw)
This patch series adds support for the AM62P SR1.2 silicon revision by
adding logic in k3-socinfo to detect AM62P variants.
This also disables HS400 support for AM62P SR1.0 and SR1.1 in sdhci host
driver and enable by default for AM62P SR1.2.
Tested against AM62P SR1.2, SR1.1, SR1.0 and AM62X SK.
Log for AM62P SR1.2:
https://gist.github.com/jmenti/3d605dcd9445c2fac86c626bfa519103
Changes since v1:
- Drop binding and DT patches
- Move disable HS400 print to sdhci_am654_init & only print if caps are
already enabled, according to Andrew's review
- Completely refactor/change patch 2/4 for k3-socinfo to not add a new
item to reg property, find GP_SW as an offset of JTAG ID. This approach
is based off-of Krzysztof's review.
Link to v1:
https://lore.kernel.org/linux-mmc/20250805234950.3781367-1-jm@ti.com
Judith Mendez (2):
soc: ti: k3-socinfo: Add support for AM62P variants
mmc: sdhci_am654: Disable HS400 for AM62P SR1.0 and SR1.1
drivers/mmc/host/sdhci_am654.c | 18 ++++++++++++++++++
drivers/soc/ti/k3-socinfo.c | 27 +++++++++++++++++++++++++--
2 files changed, 43 insertions(+), 2 deletions(-)
--
2.49.0
next reply other threads:[~2025-08-07 22:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 22:51 Judith Mendez [this message]
2025-08-07 22:51 ` [PATCH v2 1/2] soc: ti: k3-socinfo: Add support for AM62P variants Judith Mendez
2025-08-08 13:50 ` Andrew Davis
2025-08-08 14:51 ` Judith Mendez
2025-08-07 22:51 ` [PATCH v2 2/2] mmc: sdhci_am654: Disable HS400 for AM62P SR1.0 and SR1.1 Judith Mendez
2025-08-08 13:38 ` Judith Mendez
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=20250807225138.1228333-1-jm@ti.com \
--to=jm@ti.com \
--cc=adrian.hunter@intel.com \
--cc=afd@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=nm@ti.com \
--cc=ssantosh@kernel.org \
--cc=ulf.hansson@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