From: Suman Anna <s-anna@ti.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-remoteproc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
Suman Anna <s-anna@ti.com>
Subject: [PATCH 3/3] hwspinlock/omap: Add a trace during probe
Date: Thu, 30 May 2019 21:13:21 -0500 [thread overview]
Message-ID: <20190531021321.14025-4-s-anna@ti.com> (raw)
In-Reply-To: <20190531021321.14025-1-s-anna@ti.com>
Add a debug level trace statement in the OMAP HwSpinlock driver
probe function to print the number of hwlocks on a successful
registration.
Signed-off-by: Suman Anna <s-anna@ti.com>
---
drivers/hwspinlock/omap_hwspinlock.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/hwspinlock/omap_hwspinlock.c b/drivers/hwspinlock/omap_hwspinlock.c
index a4d7a7bc863a..14e1a532ebb5 100644
--- a/drivers/hwspinlock/omap_hwspinlock.c
+++ b/drivers/hwspinlock/omap_hwspinlock.c
@@ -140,6 +140,9 @@ static int omap_hwspinlock_probe(struct platform_device *pdev)
if (ret)
goto reg_fail;
+ dev_dbg(&pdev->dev, "Registered %d locks with HwSpinlock core\n",
+ num_locks);
+
return 0;
reg_fail:
--
2.21.0
WARNING: multiple messages have this Message-ID (diff)
From: Suman Anna <s-anna@ti.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
linux-remoteproc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] hwspinlock/omap: Add a trace during probe
Date: Thu, 30 May 2019 21:13:21 -0500 [thread overview]
Message-ID: <20190531021321.14025-4-s-anna@ti.com> (raw)
In-Reply-To: <20190531021321.14025-1-s-anna@ti.com>
Add a debug level trace statement in the OMAP HwSpinlock driver
probe function to print the number of hwlocks on a successful
registration.
Signed-off-by: Suman Anna <s-anna@ti.com>
---
drivers/hwspinlock/omap_hwspinlock.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/hwspinlock/omap_hwspinlock.c b/drivers/hwspinlock/omap_hwspinlock.c
index a4d7a7bc863a..14e1a532ebb5 100644
--- a/drivers/hwspinlock/omap_hwspinlock.c
+++ b/drivers/hwspinlock/omap_hwspinlock.c
@@ -140,6 +140,9 @@ static int omap_hwspinlock_probe(struct platform_device *pdev)
if (ret)
goto reg_fail;
+ dev_dbg(&pdev->dev, "Registered %d locks with HwSpinlock core\n",
+ num_locks);
+
return 0;
reg_fail:
--
2.21.0
WARNING: multiple messages have this Message-ID (diff)
From: Suman Anna <s-anna@ti.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
linux-remoteproc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] hwspinlock/omap: Add a trace during probe
Date: Thu, 30 May 2019 21:13:21 -0500 [thread overview]
Message-ID: <20190531021321.14025-4-s-anna@ti.com> (raw)
In-Reply-To: <20190531021321.14025-1-s-anna@ti.com>
Add a debug level trace statement in the OMAP HwSpinlock driver
probe function to print the number of hwlocks on a successful
registration.
Signed-off-by: Suman Anna <s-anna@ti.com>
---
drivers/hwspinlock/omap_hwspinlock.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/hwspinlock/omap_hwspinlock.c b/drivers/hwspinlock/omap_hwspinlock.c
index a4d7a7bc863a..14e1a532ebb5 100644
--- a/drivers/hwspinlock/omap_hwspinlock.c
+++ b/drivers/hwspinlock/omap_hwspinlock.c
@@ -140,6 +140,9 @@ static int omap_hwspinlock_probe(struct platform_device *pdev)
if (ret)
goto reg_fail;
+ dev_dbg(&pdev->dev, "Registered %d locks with HwSpinlock core\n",
+ num_locks);
+
return 0;
reg_fail:
--
2.21.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-05-31 2:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 2:13 [PATCH 0/3] Add HwSpinlock support for TI K3 SoCs Suman Anna
2019-05-31 2:13 ` Suman Anna
2019-05-31 2:13 ` Suman Anna
2019-05-31 2:13 ` [PATCH 1/3] dt-bindings: hwlock: Update OMAP binding " Suman Anna
2019-05-31 2:13 ` Suman Anna
2019-05-31 2:13 ` Suman Anna
2019-05-31 2:13 ` [PATCH 2/3] hwspinlock/omap: Add support " Suman Anna
2019-05-31 2:13 ` Suman Anna
2019-05-31 2:13 ` Suman Anna
2019-05-31 2:13 ` Suman Anna [this message]
2019-05-31 2:13 ` [PATCH 3/3] hwspinlock/omap: Add a trace during probe Suman Anna
2019-05-31 2:13 ` Suman Anna
2019-06-24 20:38 ` [PATCH 0/3] Add HwSpinlock support for TI K3 SoCs Suman Anna
2019-06-24 20:38 ` Suman Anna
2019-06-24 20:38 ` Suman Anna
2019-06-29 18:57 ` Bjorn Andersson
2019-06-29 18:57 ` Bjorn Andersson
2019-06-29 18:57 ` Bjorn Andersson
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=20190531021321.14025-4-s-anna@ti.com \
--to=s-anna@ti.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=robh+dt@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.