From: pramod.gurav@smartplayin.com (Pramod Gurav)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/3] Support for Qualcomm QPNP PMIC's
Date: Tue, 05 Aug 2014 12:50:41 +0530 [thread overview]
Message-ID: <53E085C9.4090302@smartplayin.com> (raw)
In-Reply-To: <1406903450-27283-1-git-send-email-svarbanov@mm-sol.com>
Hi Stanimir.
On Friday 01 August 2014 08:00 PM, Stanimir Varbanov wrote:
> Hello all,
>
> Changes since v3:
> - rename the driver to qcom-spmi-pmic - suggested by David Collins
> - spmi regmap config now initialize .fast_io to true
> - added generalized comptatible string in DT binding document and driver
> - I dropped the pm8921 rename patch for now, it will be subject of another
> patchset later on.
>
> regards,
> Stan
>
> --------------------------------------------------------------------------------
>
> Changes since v2:
> - 1/4 - added new line, signed-off-by / acked-by and module_authors.
> - 3/4 - the subject has been changed.
>
> The previous v2 can be found at [1].
>
> I'm still waiting Acks for:
> - 4/4 from Qualcomm folks.
If I am not missing something obvious, this patch needs to be resent as
it does not apply on top of patches in this series. I tried applying and
it fails in Kconfig.
> - 2/4 and 3/4 from DT folks.
>
> The patchset is ready to merge version and also it can be treated as an
> intermediate step until we find a solution for non-translatable peripheral
> addresses.
>
> [1] https://lkml.org/lkml/2014/7/17/877
>
> --------------------------------------------------------------------------------
>
> Hello everyone,
>
> Here is the continuation of patch sets sent recently about Qualcomm
> QPNP SPMI PMICs.
>
> The previous version of the patch set can be found at [1].
>
> Changes since v1:
> - removed completely custom *of* parser
> - renamed the mfd driver from qpnp-spmi to pm8xxx-spmi
> - now MFD_PM8XXX_SPMI Kconfig option depends on SPMI
>
> Removing of the custom *of* parser leads to that that the *reg* devicetree
> property cannot exist and therefore cannot be parsed to get PMIC peripheral
> resources. I took this step aside because no one from mfd drivers does this
> parsing. This will lead to inconvenience in the peripheral drivers to define
> internally the SPMI base addresses depending on the compatible property
> i.e. PMIC version.
>
> Comments are welcome!
>
> [1] https://lkml.org/lkml/2014/7/8/428
>
> --------------------------------------------------------------------------------
>
> Josh Cartwright (1):
> mfd: add support for Qualcomm SPMI PMICs
>
> Stanimir Varbanov (2):
> mfd: document DT bindings for Qualcomm SPMI PMICs
> ARM: dts: qcom: add pm8941 and pm8841 PMICs device nodes
>
> .../devicetree/bindings/mfd/qcom,spmi-pmic.txt | 64 +++++++++++++++++++
> arch/arm/boot/dts/qcom-msm8974.dtsi | 37 +++++++++++
> drivers/mfd/Kconfig | 15 +++++
> drivers/mfd/Makefile | 1 +
> drivers/mfd/qcom-spmi-pmic.c | 67 ++++++++++++++++++++
> 5 files changed, 184 insertions(+), 0 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.txt
> create mode 100644 drivers/mfd/qcom-spmi-pmic.c
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2014-08-05 7:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 14:30 [PATCH v4 0/3] Support for Qualcomm QPNP PMIC's Stanimir Varbanov
2014-08-01 14:30 ` [PATCH v4 1/3] mfd: add support for Qualcomm SPMI PMICs Stanimir Varbanov
2014-09-24 9:12 ` Lee Jones
2014-08-01 14:30 ` [PATCH v4 2/3] mfd: document DT bindings " Stanimir Varbanov
2014-08-04 13:51 ` Stanimir Varbanov
2014-09-24 9:14 ` Lee Jones
2014-08-01 14:30 ` [PATCH v4 3/3] ARM: dts: qcom: add pm8941 and pm8841 PMICs device nodes Stanimir Varbanov
2014-08-05 7:20 ` Pramod Gurav [this message]
2014-08-05 12:00 ` [PATCH v4 0/3] Support for Qualcomm QPNP PMIC's Stanimir Varbanov
2014-09-23 12:33 ` 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=53E085C9.4090302@smartplayin.com \
--to=pramod.gurav@smartplayin.com \
--cc=linux-arm-kernel@lists.infradead.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