linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Gross <agross@codeaurora.org>
To: Lina Iyer <lina.iyer@linaro.org>
Cc: bjorn.andersson@sonymobile.com, linux-arm-msm@vger.kernel.org,
	jhugo@codeaurora.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Lock 7 is cpuidle specific, use non-generic value for locking
Date: Thu, 12 Mar 2015 15:49:02 -0500	[thread overview]
Message-ID: <20150312204902.GA14659@qualcomm.com> (raw)
In-Reply-To: <1426189108-35488-1-git-send-email-lina.iyer@linaro.org>

On Thu, Mar 12, 2015 at 01:38:28PM -0600, Lina Iyer wrote:

<snip>

>  static int qcom_hwspinlock_trylock(struct hwspinlock *lock)
>  {
>  	struct regmap_field *field = lock->priv;
>  	u32 lock_owner;
>  	int ret;
> +	u32 proc_id;
>  
> -	ret = regmap_field_write(field, QCOM_MUTEX_APPS_PROC_ID);
> +	proc_id = hwspin_lock_get_id(lock) == QCOM_CPUIDLE_LOCK ?
> +			QCOM_MUTEX_CPUIDLE_OFFSET + smp_processor_id():
> +			QCOM_MUTEX_APPS_PROC_ID;
> +
> +	ret = regmap_field_write(field, proc_id);

I think I'd rather have a qcom specific function and EXPORT_SYMBOL that to deal
with this special case.

>  	if (ret)
>  		return ret;
>  
> @@ -42,7 +49,7 @@ static int qcom_hwspinlock_trylock(struct hwspinlock *lock)
>  	if (ret)
>  		return ret;
>  
> -	return lock_owner == QCOM_MUTEX_APPS_PROC_ID;
> +	return lock_owner == proc_id;
>  }
>  
>  static void qcom_hwspinlock_unlock(struct hwspinlock *lock)
> -- 
> 2.1.0
> 

-- 
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project


  parent reply	other threads:[~2015-03-12 20:49 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 22:30 [PATCH v6 1/2] DT: hwspinlock: Add binding documentation for Qualcomm hwmutex Bjorn Andersson
2015-02-27 22:30 ` [PATCH v6 2/2] hwspinlock: qcom: Add support for Qualcomm HW Mutex block Bjorn Andersson
2015-03-11 21:09   ` Andy Gross
2015-03-12 19:31   ` Lina Iyer
2015-03-12 19:43     ` Andy Gross
2015-03-12 19:55       ` Lina Iyer
2015-03-18 16:10         ` Bjorn Andersson
2015-03-18 15:55     ` Bjorn Andersson
2015-03-18 16:45       ` Lina Iyer
2015-03-18 21:59         ` Bjorn Andersson
2015-03-12 19:38   ` [PATCH] Lock 7 is cpuidle specific, use non-generic value for locking Lina Iyer
2015-03-12 20:35     ` Stephen Boyd
2015-03-12 20:48       ` Lina Iyer
2015-03-12 21:12         ` Stephen Boyd
2015-03-12 22:16           ` Lina Iyer
2015-03-13 20:02             ` Andy Gross
2015-03-13 21:27               ` Lina Iyer
2015-03-12 20:49     ` Andy Gross [this message]
2015-03-12 20:56       ` Lina Iyer
2015-03-12 22:29   ` [PATCH v6 2/2] hwspinlock: qcom: Add support for Qualcomm HW Mutex block Lina Iyer
2015-03-18 16:12     ` Bjorn Andersson
2015-03-18 19:41       ` Lina Iyer
2015-03-16 22:38   ` Jeffrey Hugo
2015-03-02  5:05 ` [PATCH v6 1/2] DT: hwspinlock: Add binding documentation for Qualcomm hwmutex Andy Gross
2015-03-12  9:29 ` Ohad Ben-Cohen
2015-04-01 21:32   ` Tim Bird
2015-04-02  4:40     ` Ohad Ben-Cohen
2015-04-02 18:11       ` Tim Bird
2015-04-03 13:55         ` Ohad Ben-Cohen
2015-04-06 16:22           ` Tim Bird
2015-04-06 16:31             ` Ohad Ben-Cohen
2015-04-06 16:48               ` Bjorn Andersson
2015-04-06 19:04                 ` Ohad Ben-Cohen
2015-04-13 10:23                   ` Ohad Ben-Cohen
2015-04-15 19:40                     ` Rob Herring
2015-04-16 12:01                       ` Mark Rutland
2015-03-12  9:51 ` Mark Rutland
2015-03-12 11:14   ` Bjorn Andersson
2015-03-16 22:35 ` Jeffrey Hugo
2015-04-14 19:18 ` Kumar Gala
2015-04-15 18:20   ` Ohad Ben-Cohen
2015-04-16 11:52 ` Mark Rutland

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=20150312204902.GA14659@qualcomm.com \
    --to=agross@codeaurora.org \
    --cc=bjorn.andersson@sonymobile.com \
    --cc=jhugo@codeaurora.org \
    --cc=lina.iyer@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.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 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).