From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
devicetree@vger.kernel.org,
"Peter Ujfalusi" <peter.ujfalusi@ti.com>
Subject: [PATCH 01/14] bus: ti-sysc: Detect EDMA and set quirk flags for tptc
Date: Tue, 3 Mar 2020 14:15:15 -0800 [thread overview]
Message-ID: <20200303221528.49099-2-tony@atomide.com> (raw)
In-Reply-To: <20200303221528.49099-1-tony@atomide.com>
In order to probe EDMA with ti-sysc interconnect target module and with
device tree data, we need to properly detect EDMA and set the flags for
SYSC_QUIRK_SWSUP_SIDLE | SYSC_QUIRK_SWSUP_MSTANDBY for tptc.
We have these flags currently set for am4 and dra7, but not for am335x.
Let's set them for all the SoCs as the tptc module should behave the
same for all of them. It's likely that am335x was never tested to idle
EDMA tptc.
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
---
drivers/bus/ti-sysc.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/drivers/bus/ti-sysc.c b/drivers/bus/ti-sysc.c
--- a/drivers/bus/ti-sysc.c
+++ b/drivers/bus/ti-sysc.c
@@ -1331,6 +1331,10 @@ static const struct sysc_revision_quirk sysc_revision_quirks[] = {
SYSC_MODULE_QUIRK_SGX),
SYSC_QUIRK("rtc", 0, 0x74, 0x78, -ENODEV, 0x4eb01908, 0xffff00f0,
SYSC_MODULE_QUIRK_RTC_UNLOCK),
+ SYSC_QUIRK("tptc", 0, 0, 0x10, -ENODEV, 0x40006c00, 0xffffefff,
+ SYSC_QUIRK_SWSUP_SIDLE | SYSC_QUIRK_SWSUP_MSTANDBY),
+ SYSC_QUIRK("tptc", 0, 0, -ENODEV, -ENODEV, 0x40007c00, 0xffffffff,
+ SYSC_QUIRK_SWSUP_SIDLE | SYSC_QUIRK_SWSUP_MSTANDBY),
SYSC_QUIRK("usb_otg_hs", 0, 0x400, 0x404, 0x408, 0x00000050,
0xffffffff, SYSC_QUIRK_SWSUP_SIDLE | SYSC_QUIRK_SWSUP_MSTANDBY),
SYSC_QUIRK("usb_otg_hs", 0, 0, 0x10, -ENODEV, 0x4ea2080d, 0xffffffff,
@@ -1397,6 +1401,7 @@ static const struct sysc_revision_quirk sysc_revision_quirks[] = {
SYSC_QUIRK("spinlock", 0, 0, 0x10, -ENODEV, 0x50020000, 0xffffffff, 0),
SYSC_QUIRK("rng", 0, 0x1fe0, 0x1fe4, -ENODEV, 0x00000020, 0xffffffff, 0),
SYSC_QUIRK("timer32k", 0, 0, 0x4, -ENODEV, 0x00000060, 0xffffffff, 0),
+ SYSC_QUIRK("tpcc", 0, 0, -ENODEV, -ENODEV, 0x40014c00, 0xffffffff, 0),
SYSC_QUIRK("usbhstll", 0, 0, 0x10, 0x14, 0x00000004, 0xffffffff, 0),
SYSC_QUIRK("usbhstll", 0, 0, 0x10, 0x14, 0x00000008, 0xffffffff, 0),
SYSC_QUIRK("usb_host_hs", 0, 0, 0x10, 0x14, 0x50700100, 0xffffffff, 0),
--
2.25.1
next prev parent reply other threads:[~2020-03-03 22:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 22:15 [PATCH 00/14] Probe EDMA with dts data for am3, am4 and dra7 Tony Lindgren
2020-03-03 22:15 ` Tony Lindgren [this message]
2020-03-03 22:15 ` [PATCH 02/14] ARM: dts: Configure interconnect target module for am3 tpcc Tony Lindgren
2020-03-03 22:15 ` [PATCH 03/14] ARM: dts: Configure interconnect target module for am3 tptc0 Tony Lindgren
2020-03-03 22:15 ` [PATCH 04/14] ARM: dts: Configure interconnect target module for am3 tptc1 Tony Lindgren
2020-03-03 22:15 ` [PATCH 05/14] ARM: dts: Configure interconnect target module for am3 tptc2 Tony Lindgren
2020-03-03 22:15 ` [PATCH 06/14] ARM: dts: Configure interconnect target module for am4 tpcc Tony Lindgren
2020-03-03 22:15 ` [PATCH 07/14] ARM: dts: Configure interconnect target module for am4 tptc0 Tony Lindgren
2020-03-03 22:15 ` [PATCH 08/14] ARM: dts: Configure interconnect target module for am4 tptc1 Tony Lindgren
2020-03-03 22:15 ` [PATCH 09/14] ARM: dts: Configure interconnect target module for am4 tptc2 Tony Lindgren
2020-03-03 22:15 ` [PATCH 10/14] ARM: OMAP2+: Drop legacy platform data for am3 and am4 edma Tony Lindgren
2020-03-03 22:15 ` [PATCH 11/14] ARM: dts: Configure interconnect target module for dra7 tpcc Tony Lindgren
2020-03-03 22:15 ` [PATCH 12/14] ARM: dts: Configure interconnect target module for dra7 tptc0 Tony Lindgren
2020-03-03 22:15 ` [PATCH 13/14] ARM: dts: Configure interconnect target module for dra7 tptc1 Tony Lindgren
2020-03-03 22:15 ` [PATCH 14/14] ARM: OMAP2+: Drop legacy platform data for dra7 edma Tony Lindgren
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=20200303221528.49099-2-tony@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.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).