From: Vignesh Raghavendra <vigneshr@ti.com>
To: u-boot@lists.denx.de
Subject: [PATCH v4 04/10] soc: ti: k3-navss-ringacc: Get SYSFW reference from DT phandle
Date: Mon, 9 Dec 2019 10:25:34 +0530 [thread overview]
Message-ID: <20191209045540.10702-5-vigneshr@ti.com> (raw)
In-Reply-To: <20191209045540.10702-1-vigneshr@ti.com>
Instead of looking getting reference to SYSFW device using name which
is not guaranteed to be constant, use phandle supplied in the DT node to
get reference to SYSFW
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
Reviewed-by: Grygorii Strashko <grygorii.strashko@ti.com>
---
drivers/soc/ti/k3-navss-ringacc.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/soc/ti/k3-navss-ringacc.c b/drivers/soc/ti/k3-navss-ringacc.c
index f06ea29c986c..17949d2d0a67 100644
--- a/drivers/soc/ti/k3-navss-ringacc.c
+++ b/drivers/soc/ti/k3-navss-ringacc.c
@@ -942,7 +942,8 @@ static int k3_nav_ringacc_probe_dt(struct k3_nav_ringacc *ringacc)
ringacc->dma_ring_reset_quirk =
dev_read_bool(dev, "ti,dma-ring-reset-quirk");
- ret = uclass_get_device_by_name(UCLASS_FIRMWARE, "dmsc", &tisci_dev);
+ ret = uclass_get_device_by_phandle(UCLASS_FIRMWARE, dev,
+ "ti,sci", &tisci_dev);
if (ret) {
pr_debug("TISCI RA RM get failed (%d)\n", ret);
ringacc->tisci = NULL;
--
2.24.0
next prev parent reply other threads:[~2019-12-09 4:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 4:55 [PATCH v4 00/10] dma: ti: k3-udma: Add support for J721e Vignesh Raghavendra
2019-12-09 4:55 ` [PATCH v4 01/10] lib: Import few bitmap functions from Linux Vignesh Raghavendra
2019-12-09 4:55 ` [PATCH v4 02/10] dma: ti: k3-udma: Query DMA channels allocated from Resource Manager Vignesh Raghavendra
2019-12-09 4:55 ` [PATCH v4 03/10] soc: ti: k3-navss-ringacc: Flush/invalidate caches on ring push/pop Vignesh Raghavendra
2019-12-09 4:55 ` Vignesh Raghavendra [this message]
2019-12-09 4:55 ` [PATCH v4 05/10] dma: ti: k3-udma: Remove coherency check for cache ops Vignesh Raghavendra
2019-12-09 4:55 ` [PATCH v4 06/10] dma: ti: k3-udma: Fix debug prints during enabling MEM_TO_DEV transfers Vignesh Raghavendra
2019-12-09 4:55 ` [PATCH v4 07/10] dma: ti: k3-udma: Switch to exposed ring mode Vignesh Raghavendra
2019-12-09 4:55 ` [PATCH v4 08/10] dma: ti: k3-udma: Fix ring push operation for 32 bit cores Vignesh Raghavendra
2019-12-09 4:55 ` [PATCH v4 09/10] dma: ti: k3-udma: Fix build warnings when building for 32 bit platforms Vignesh Raghavendra
2019-12-09 4:55 ` [PATCH v4 10/10] dma: ti: k3-udma: Add new compatible to J721e Vignesh Raghavendra
2020-01-20 5:58 ` [PATCH v4 00/10] dma: ti: k3-udma: Add support for J721e Lokesh Vutla
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=20191209045540.10702-5-vigneshr@ti.com \
--to=vigneshr@ti.com \
--cc=u-boot@lists.denx.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