From: Kumar Gala <galak@codeaurora.org>
To: Suman Anna <s-anna@ti.com>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
Tony Lindgren <tony@atomide.com>,
Benoit Cousson <bcousson@baylibre.com>,
<linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH 1/2] hwspinlock/omap: add support for dt nodes
Date: Tue, 3 Sep 2013 13:50:53 -0500 [thread overview]
Message-ID: <43798031-2D57-44F0-A19C-FD80DB9E9794@codeaurora.org> (raw)
In-Reply-To: <1378230767-54931-1-git-send-email-s-anna@ti.com>
On Sep 3, 2013, at 12:52 PM, Suman Anna wrote:
> HwSpinlock IP is present only on OMAP4 and other newer SoCs,
> which are all device-tree boot only. This patch adds the
> base support for parsing the DT nodes, and removes the code
> dealing with the traditional platform device instantiation.
>
> Signed-off-by: Suman Anna <s-anna@ti.com>
> ---
> .../devicetree/bindings/hwlock/omap-hwspinlock.txt | 28 ++++++++++
> arch/arm/mach-omap2/Makefile | 3 --
> arch/arm/mach-omap2/hwspinlock.c | 60 ----------------------
> drivers/hwspinlock/omap_hwspinlock.c | 21 ++++++--
> 4 files changed, 45 insertions(+), 67 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/hwlock/omap-hwspinlock.txt
> delete mode 100644 arch/arm/mach-omap2/hwspinlock.c
>
> diff --git a/Documentation/devicetree/bindings/hwlock/omap-hwspinlock.txt b/Documentation/devicetree/bindings/hwlock/omap-hwspinlock.txt
> new file mode 100644
> index 0000000..adfb8ad
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/hwlock/omap-hwspinlock.txt
> @@ -0,0 +1,28 @@
> +OMAP4+ HwSpinlock Driver
> +
> +Required properties:
> +- compatible: Currently supports only "ti,omap4-hwspinlock" for
> + OMAP44xx, OMAP54xx, AM33xx, AM43xx, DRA7xx SoCs
> +- reg: Contains the hwspinlock register address range (base
> + address and length)
> +- ti,hwmods: Name of the hwmod associated with the hwspinlock device
> +
> +Optional properties:
> +- base_id: Base Id for the locks for a particular hwspinlock
> + device. If not mentioned, a default value of 0 is used.
> + This property is mandatory ONLY if a SoC has several
> + hwspinlock devices. There are currently no such OMAP
> + SoCs.
Should this be ti,base_id ? [ I know its kinda generic in its intent for any SoC w/multiple blocks ]
> +
> + See documentation on struct hwspinlock_pdata in
> + linux/hwspinlock.h for more details.
> +
> +
> +Example:
> +
> +/* OMAP4 */
> +hwspinlock: spinlock@4a0f6000 {
> + compatible = "ti,omap4-hwspinlock";
> + reg = <0x4a0f6000 0x1000>;
> + ti,hwmods = "spinlock";
> +};
[ snip ]
- k
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2013-09-03 18:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 17:52 Suman Anna
2013-09-03 18:50 ` Kumar Gala [this message]
2013-09-03 19:10 ` Suman Anna
2013-09-03 19:37 ` Kumar Gala
2013-09-03 22:34 ` Suman Anna
2013-09-04 14:46 ` Kumar Gala
2013-09-04 16:27 ` Suman Anna
2013-09-04 16:42 ` Kumar Gala
2013-09-04 17:03 ` Suman Anna
2013-09-04 17:51 ` Kumar Gala
2013-09-04 20:04 ` Suman Anna
2013-09-04 8:09 ` Stanimir Varbanov
2013-09-04 16:30 ` Suman Anna
2013-10-03 18:05 ` Tony Lindgren
2013-10-03 18:16 ` Suman Anna
2013-10-03 18:19 ` 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=43798031-2D57-44F0-A19C-FD80DB9E9794@codeaurora.org \
--to=galak@codeaurora.org \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=s-anna@ti.com \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®