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>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Maxime Ripard <mripard@kernel.org>,
Roger Quadros <rogerq@kernel.org>, Nikhil Jain <n-jain1@ti.com>,
Andrew Davis <afd@ti.com>,
Ravi Gunasekaran <r-gunasekaran@ti.com>,
Nishanth Menon <nm@ti.com>
Subject: [PATCH V3 2/3] arm: mach-k3: am62: Add timer0 id to the dev list
Date: Thu, 27 Jul 2023 04:03:30 -0500 [thread overview]
Message-ID: <20230727090331.2834463-3-nm@ti.com> (raw)
In-Reply-To: <20230727090331.2834463-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>
Reviewed-by: Roger Quadros <rogerq@kernel.org>
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>
Signed-off-by: Nishanth Menon <nm@ti.com>
---
Changes since V2:
- Added Roger's reviewed-by
V2: https://lore.kernel.org/all/20230726151027.2517151-3-nm@ti.com/
V1: https://lore.kernel.org/all/20230725125856.1807742-3-nm@ti.com/
Original patch: https://lore.kernel.org/r/20230406185542.1179073-3-sjoerd@collabora.com
arch/arm/mach-k3/am62x/dev-data.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-k3/am62x/dev-data.c b/arch/arm/mach-k3/am62x/dev-data.c
index 1a6f9e2ca03e..59c95df2a887 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]),
--
2.40.0
next prev parent reply other threads:[~2023-07-27 9:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 9:03 [PATCH V3 0/3] arm: dts: Sync k3-am62 with upstream kernel Nishanth Menon
2023-07-27 9:03 ` [PATCH V3 1/3] omap: timer: add ti,am654-timer compatibility Nishanth Menon
2023-07-28 16:50 ` Tom Rini
2023-07-27 9:03 ` Nishanth Menon [this message]
2023-07-28 16:50 ` [PATCH V3 2/3] arm: mach-k3: am62: Add timer0 id to the dev list Tom Rini
2023-07-27 9:03 ` [PATCH V3 3/3] arm: dts: k3-am62: Bump dtsi from linux v6.5-rc1 Nishanth Menon
2023-07-28 12:45 ` Maxime Ripard
2023-07-28 16:51 ` Tom Rini
2023-07-28 12:45 ` [PATCH V3 0/3] arm: dts: Sync k3-am62 with upstream kernel 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=20230727090331.2834463-3-nm@ti.com \
--to=nm@ti.com \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=francesco@dolcini.it \
--cc=marcel.ziswiler@toradex.com \
--cc=mkorpershoek@baylibre.com \
--cc=mripard@kernel.org \
--cc=n-francis@ti.com \
--cc=n-jain1@ti.com \
--cc=r-gunasekaran@ti.com \
--cc=rogerq@kernel.org \
--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