public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gilad Avidov <gavidov@codeaurora.org>
To: gavidov@codeaurora.org, sdharia@codeaurora.org,
	mlocke@codeaurora.org, linux-arm-msm@vger.kernel.org,
	gregkh@linuxfoundation.org, svarbanov@mm-sol.com
Cc: linux-kernel@vger.kernel.org, iivanov@mm-sol.com,
	galak@codeaurora.org, agross@codeaurora.org
Subject: [PATCH V2 1/2] spmi: remove wakeup command before slave probe
Date: Fri, 30 Jan 2015 17:46:40 -0700	[thread overview]
Message-ID: <1422665201-25569-2-git-send-email-gavidov@codeaurora.org> (raw)
In-Reply-To: <1422665201-25569-1-git-send-email-gavidov@codeaurora.org>

According to spmi spec a slave powers up into startup state and then
transitions into active state. Thus, the wakeup command is not required
before calling the slave's probe. The wakeup command is only needed for
slaves that are in sleep state after receiving the sleep command.

This is a bug since spmi master controllers, such as spmi-pmic-arb,
which have no support for wakeup command return an error on that
command and thus fail before reaching a slave driver probe.

Cc: galak@codeaurora.org
Acked-by: Sagar Dharia <sdharia@codeaurora.org>
Signed-off-by: Gilad Avidov <gavidov@codeaurora.org>
---
 drivers/spmi/spmi.c | 8 +-------
 1 file changed, 1 insertion(+), 7 deletions(-)

diff --git a/drivers/spmi/spmi.c b/drivers/spmi/spmi.c
index 1d92f51..9ff7454 100644
--- a/drivers/spmi/spmi.c
+++ b/drivers/spmi/spmi.c
@@ -1,4 +1,4 @@
-/* Copyright (c) 2012-2013, The Linux Foundation. All rights reserved.
+/* Copyright (c) 2012-2015, The Linux Foundation. All rights reserved.
  *
  * This program is free software; you can redistribute it and/or modify
  * it under the terms of the GNU General Public License version 2 and
@@ -316,11 +316,6 @@ static int spmi_drv_probe(struct device *dev)
 	struct spmi_device *sdev = to_spmi_device(dev);
 	int err;
 
-	/* Ensure the slave is in ACTIVE state */
-	err = spmi_command_wakeup(sdev);
-	if (err)
-		goto fail_wakeup;
-
 	pm_runtime_get_noresume(dev);
 	pm_runtime_set_active(dev);
 	pm_runtime_enable(dev);
@@ -335,7 +330,6 @@ fail_probe:
 	pm_runtime_disable(dev);
 	pm_runtime_set_suspended(dev);
 	pm_runtime_put_noidle(dev);
-fail_wakeup:
 	return err;
 }
 
-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation


  reply	other threads:[~2015-01-31  0:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-31  0:46 [PATCH V2 0/2] add support for pmic_arb v2 and correct framework Gilad Avidov
2015-01-31  0:46 ` Gilad Avidov [this message]
2015-02-03  9:36   ` [PATCH V2 1/2] spmi: remove wakeup command before slave probe Stanimir Varbanov
2015-02-04  1:17     ` Gilad Avidov
2015-01-31  0:46 ` [PATCH V2 2/2] spmi: pmic_arb: add support for hw version 2 Gilad Avidov
2015-02-03  9:59   ` Stanimir Varbanov
2015-02-03 16:59     ` Gilad Avidov
2015-02-03 17:14       ` Stanimir Varbanov
2015-02-03 21:21     ` Lina Iyer
2015-02-04 14:36       ` Stanimir Varbanov

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=1422665201-25569-2-git-send-email-gavidov@codeaurora.org \
    --to=gavidov@codeaurora.org \
    --cc=agross@codeaurora.org \
    --cc=galak@codeaurora.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=iivanov@mm-sol.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mlocke@codeaurora.org \
    --cc=sdharia@codeaurora.org \
    --cc=svarbanov@mm-sol.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