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
Cc: linux-kernel@vger.kernel.org, iivanov@mm-sol.com, galak@codeaurora.org,
        agross@codeaurora.org
Subject: [PATCH V4 0/2] [PATCH V4 0/2] add support for pmic_arb v2 and correct framework
Date: Thu, 19 Feb 2015 15:54:11 -0700
Message-Id: <1424386453-18092-1-git-send-email-gavidov@codeaurora.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1563
Lines: 37

pmic_arb v2 has no support for spmi non-data commands and thus
returns -EOPNOTSUPP on .cmd callback. This causes a failure in
spmi_drv_probe() which sends a wakeup command to the slave before
probing its driver. This patchset removes the wakeup from
spmi_drv_probe() since the spmi spec stipulates that a slaves
default state is active and doesn't need a wakeup.

Changelog from v3 to v4:

spmi: remove wakeup command before slave probe:
1. Remove the claim that this is a bug fix off the commit text.

spmi: pmic_arb: add support for hw version 2
1. Unmap the core register space as soon as we know that it will not be used
   (on v2 it is used only to read the hw version in probe).
3. Assign the core reg space to a local until we know if it appropriate to use
   it to configure the controller fields (on v1) or unmap it (on v2).


Gilad Avidov (2):
  spmi: remove wakeup command before slave probe
  spmi: pmic_arb: add support for hw version 2

 .../bindings/spmi/qcom,spmi-pmic-arb.txt           |   6 +-
 drivers/spmi/spmi-pmic-arb.c                       | 315 +++++++++++++++++----
 drivers/spmi/spmi.c                                |   9 +-
 3 files changed, 266 insertions(+), 64 deletions(-)

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/