From: Bjorn Andersson <bjorn.andersson-/MT0OVThwyLZJqsBc5GL+g@public.gmane.org>
To: Suman Anna <s-anna-l0cyMroinI0@public.gmane.org>
Cc: Ohad Ben-Cohen <ohad-Ix1uc/W3ht7QT0dZR+AlfA@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH v8 2/4] hwspinlock/core: add device tree support
Date: Thu, 12 Mar 2015 04:05:43 -0700 [thread overview]
Message-ID: <20150312110543.GT26334@sonymobile.com> (raw)
In-Reply-To: <1425520876-37826-3-git-send-email-s-anna-l0cyMroinI0@public.gmane.org>
On Wed 04 Mar 18:01 PST 2015, Suman Anna wrote:
> This patch adds a new OF-friendly API of_hwspin_lock_get_id()
> for hwspinlock clients to use/request locks from a hwspinlock
> device instantiated through a device-tree blob. This new API
> can be used by hwspinlock clients to get the id for a specific
> lock using the phandle + args specifier, so that it can be
> requested using the available hwspin_lock_request_specific()
> API.
>
> Signed-off-by: Suman Anna <s-anna-l0cyMroinI0@public.gmane.org>
Reviewed-by: Bjorn Andersson <bjorn.andersson-/MT0OVThwyLZJqsBc5GL+g@public.gmane.org>
Regards,
Bjorn
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-03-12 11:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 2:01 [PATCH v8 0/4] hwspinlock core & omap dt support Suman Anna
2015-03-05 2:01 ` [PATCH v8 2/4] hwspinlock/core: add device tree support Suman Anna
[not found] ` <1425520876-37826-3-git-send-email-s-anna-l0cyMroinI0@public.gmane.org>
2015-03-12 11:05 ` Bjorn Andersson [this message]
2015-03-05 2:01 ` [PATCH v8 3/4] Documentation: dt: add the omap hwspinlock bindings document Suman Anna
2015-03-05 2:01 ` [PATCH v8 4/4] hwspinlock/omap: add support for dt nodes Suman Anna
[not found] ` <1425520876-37826-1-git-send-email-s-anna-l0cyMroinI0@public.gmane.org>
2015-03-05 2:01 ` [PATCH v8 1/4] Documentation: dt: add common bindings for hwspinlock Suman Anna
2015-03-12 9:24 ` [PATCH v8 0/4] hwspinlock core & omap dt support Ohad Ben-Cohen
2015-03-18 21:57 ` Suman Anna
2015-04-02 16:40 ` Suman Anna
2015-04-16 9:31 ` Mark Rutland
2015-04-16 10:28 ` Ohad Ben-Cohen
[not found] ` <CAK=WgbYJAnc_DFbqc3nJfYGWfqk4Krgi_BuJ=UXUNHHA-hvzKw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-02 7:55 ` Ohad Ben-Cohen
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=20150312110543.GT26334@sonymobile.com \
--to=bjorn.andersson-/mt0ovthwylzjqsbc5gl+g@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=ohad-Ix1uc/W3ht7QT0dZR+AlfA@public.gmane.org \
--cc=s-anna-l0cyMroinI0@public.gmane.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 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).