From: Varun Wadekar <vwadekar-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Thierry Reding
<thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
Cc: "ohad-Ix1uc/W3ht7QT0dZR+AlfA@public.gmane.org"
<ohad-Ix1uc/W3ht7QT0dZR+AlfA@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] hwspinlock: core: support for TEGRA hardware spinlocks
Date: Tue, 15 Nov 2011 13:42:57 +0530 [thread overview]
Message-ID: <4EC21F09.5050206@nvidia.com> (raw)
In-Reply-To: <20111115065104.GA5705-RM9K5IK7kjIQXX3q8xo1gnVAuStQJXxyR5q1nwbD4aMs9pC9oP6+/A@public.gmane.org>
>> TEGRA has a hardware spinlock block which is used
>> to get exclusive access to the hardware blocks either
>> from the CPU or the COP. The TEGRA hardware spinlock
>> block has the capability to interrupt the requester
>> on success. For this the core need not disable
>> preemption or interrupts before calling into the
>> actual driver. Add lock_timeout to the ops structure
>> to facilitate this working and to maintain backward
>> compatibility.
> You're using "TEGRA" in the patch description, but below it is spelled
> "Tegra". Should this be made consistent?
>
> Also, this patch should probably be paired with a patch that actually uses
> the new field. That would make it easier to understand the reason for this
> change.
>
Actually, the basic idea is to keep preemption and interrupts enabled
for SoCs similar to Tegra. Since the previous architecture is designed
for the OMAP line of preocessors, fitting the Tegra hwspinlock driver
was not possible. Instead of going about changing the framework and then
the OMAP drivers, I thought of adding another callback to the ops
structure which can sleep and does not need interrupts to be disabled.
prev parent reply other threads:[~2011-11-15 8:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 5:19 [PATCH] hwspinlock: core: support for TEGRA hardware spinlocks Varun Wadekar
[not found] ` <1321334342-3283-1-git-send-email-vwadekar-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-11-15 6:24 ` Varun Wadekar
[not found] ` <4EC205AC.4000202-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-11-17 5:13 ` Varun Wadekar
[not found] ` <4EC4980A.6060409-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-11-17 6:07 ` Ohad Ben-Cohen
[not found] ` <CAK=WgbY1DLQWJk-OEAfLGCECUQCkVY8ad1jZxzxeUfOuvLJsvg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-17 8:18 ` Varun Wadekar
2011-11-21 10:21 ` Ohad Ben-Cohen
2011-11-15 6:51 ` Thierry Reding
[not found] ` <20111115065104.GA5705-RM9K5IK7kjIQXX3q8xo1gnVAuStQJXxyR5q1nwbD4aMs9pC9oP6+/A@public.gmane.org>
2011-11-15 8:12 ` Varun Wadekar [this message]
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=4EC21F09.5050206@nvidia.com \
--to=vwadekar-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ohad-Ix1uc/W3ht7QT0dZR+AlfA@public.gmane.org \
--cc=thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@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