From: Nishanth Menon <nm@ti.com>
To: <u-boot@lists.denx.de>, Tom Rini <trini@konsulko.com>
Cc: Wadim Egorov <w.egorov@phytec.de>,
Francesco Dolcini <francesco@dolcini.it>,
Sjoerd Simons <sjoerd@collabora.com>,
Neha Malcom Francis <n-francis@ti.com>,
Bryan Brattlof <bb@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Nitin Yadav <n-yadav@ti.com>,
Ravi Gunasekaran <r-gunasekaran@ti.com>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
Nishanth Menon <nm@ti.com>
Subject: [RFC PATCH 2/4] arm: mach-k3: am62: Add timer0 id to the dev list
Date: Thu, 13 Jul 2023 02:20:17 -0500 [thread overview]
Message-ID: <20230713072019.3153871-3-nm@ti.com> (raw)
In-Reply-To: <20230713072019.3153871-1-nm@ti.com>
From: Sjoerd Simons <sjoerd@collabora.com>
Timer0 is used by u-boot as the tick timer; Add it to the soc devices
list so it can be enabled via the k3 power controller.
Signed-off-by: Sjoerd Simons <sjoerd@collabora.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
Tested-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
Tested-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
Cc: Francesco Dolcini <francesco@dolcini.it>
Cc: Wadim Egorov <w.egorov@phytec.de>
[nm@ti.com: Fixup num_devices]
Signed-off-by: Nishanth Menon <nm@ti.com>
---
Changes since Sjoerd's revision:
I fixed up the num_devs to be 22.
V1: https://lore.kernel.org/r/20230406185542.1179073-3-sjoerd@collabora.com
arch/arm/mach-k3/am62x/dev-data.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/mach-k3/am62x/dev-data.c b/arch/arm/mach-k3/am62x/dev-data.c
index 616d0650b9c0..c747769cf05c 100644
--- a/arch/arm/mach-k3/am62x/dev-data.c
+++ b/arch/arm/mach-k3/am62x/dev-data.c
@@ -58,6 +58,7 @@ static struct ti_dev soc_dev_list[] = {
PSC_DEV(161, &soc_lpsc_list[8]),
PSC_DEV(162, &soc_lpsc_list[9]),
PSC_DEV(75, &soc_lpsc_list[10]),
+ PSC_DEV(36, &soc_lpsc_list[11]),
PSC_DEV(102, &soc_lpsc_list[11]),
PSC_DEV(146, &soc_lpsc_list[11]),
PSC_DEV(13, &soc_lpsc_list[12]),
@@ -74,5 +75,5 @@ const struct ti_k3_pd_platdata am62x_pd_platdata = {
.num_psc = 2,
.num_pd = 5,
.num_lpsc = 16,
- .num_devs = 21,
+ .num_devs = 22,
};
--
2.40.0
next prev parent reply other threads:[~2023-07-13 7:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 7:20 [RFC PATCH 0/4] arm: dts: Sync k3-am62 with upstream Nishanth Menon
2023-07-13 7:20 ` [RFC PATCH 1/4] omap: timer: add ti,am654-timer compatibility Nishanth Menon
2023-07-13 7:20 ` Nishanth Menon [this message]
2023-07-13 11:38 ` [RFC PATCH 2/4] arm: mach-k3: am62: Add timer0 id to the dev list Ravi Gunasekaran
2023-07-13 18:35 ` Nishanth Menon
2023-07-13 18:59 ` Bryan Brattlof
2023-07-13 7:20 ` [RFC PATCH 3/4] arm: dts: Fix build of am62a7 dtbs Nishanth Menon
2023-07-13 9:11 ` Mattijs Korpershoek
2023-07-13 19:00 ` Bryan Brattlof
2023-07-13 19:38 ` Nishanth Menon
2023-07-13 7:20 ` [RFC PATCH 4/4] arm: dts: k3-am62: Bump dtsi from linux v6.5-rc1 Nishanth Menon
2023-07-19 8:27 ` Maxime Ripard
2023-07-19 14:05 ` Nishanth Menon
2023-07-19 14:14 ` Maxime Ripard
2023-07-19 17:22 ` Nishanth Menon
2023-07-20 15:24 ` Roger Quadros
2023-07-17 12:27 ` [RFC PATCH 0/4] arm: dts: Sync k3-am62 with upstream Maxime Ripard
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=20230713072019.3153871-3-nm@ti.com \
--to=nm@ti.com \
--cc=bb@ti.com \
--cc=francesco@dolcini.it \
--cc=mkorpershoek@baylibre.com \
--cc=n-francis@ti.com \
--cc=n-yadav@ti.com \
--cc=r-gunasekaran@ti.com \
--cc=sjoerd@collabora.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
--cc=w.egorov@phytec.de \
/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