From: Guru Das Srinagesh <email@example.com> To: Lee Jones <firstname.lastname@example.org>, Rob Herring <email@example.com>, firstname.lastname@example.org Cc: Mark Brown <email@example.com>, linux-arm-msm <firstname.lastname@example.org>, Bjorn Andersson <email@example.com>, firstname.lastname@example.org, Guru Das Srinagesh <email@example.com> Subject: [PATCH v4 0/3] Add Qualcomm Technologies, Inc. PM8008 MFD driver Date: Mon, 10 May 2021 17:27:05 -0700 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) Changes from v3: - Addressed Lee's comments. - This patchset is still based on regmap.git's for-next branch as my regmap-irq changes have not yet landed in mfd.git for-mfd-next or for-mfd-next-next (please advise which branch to use in this regard). Changes from v2: - Collected Rob Herring's Acked-by for the IRQ listing patch - Addressed Rob's comments for the dt-bindings patch Changes from v1: - Removed errant Change-Id from dt-bindings IRQ patch and gathered Bjorn's Reviewed-by - Fixed up YAML errors using make dt_binding_check This driver is dependent on changes that have been made to the regmap-irq framework that have currently been accepted  in regmap.git upstream by Mark Brown but haven't made it to Linus' tree yet. For this reason, this driver has been based on the tip of regmap.git and not mfd.git. Those changes, and this driver, are the result of a rewrite effort that was promised a long ago . The framework changes and this driver have been tested and verified end-to-end on an internal platform.  https://lore.kernel.org/lkml/20210318183607.gFxO2hoTO274vl3jUuxWbi19rq9wQELzN-y3B4jvO10@z/  https://email@example.com/  https://lore.kernel.org/lkml/20200519185757.GA13992@codeaurora.org/ Guru Das Srinagesh (3): dt-bindings: mfd: pm8008: Add IRQ listing dt-bindings: mfd: pm8008: Add bindings mfd: pm8008: Add driver for QCOM PM8008 PMIC .../devicetree/bindings/mfd/qcom,pm8008.yaml | 121 ++++++++++ drivers/mfd/Kconfig | 14 ++ drivers/mfd/Makefile | 1 + drivers/mfd/qcom-pm8008.c | 260 +++++++++++++++++++++ include/dt-bindings/mfd/qcom-pm8008.h | 19 ++ 5 files changed, 415 insertions(+) create mode 100644 Documentation/devicetree/bindings/mfd/qcom,pm8008.yaml create mode 100644 drivers/mfd/qcom-pm8008.c create mode 100644 include/dt-bindings/mfd/qcom-pm8008.h -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project
next reply other threads:[~2021-05-11 0:27 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-11 0:27 Guru Das Srinagesh [this message] 2021-05-11 0:27 ` [PATCH v4 1/3] dt-bindings: mfd: pm8008: Add IRQ listing Guru Das Srinagesh 2021-05-11 0:27 ` [PATCH v4 2/3] dt-bindings: mfd: pm8008: Add bindings Guru Das Srinagesh 2021-05-11 0:40 ` Guru Das Srinagesh 2021-05-11 0:27 ` [PATCH v4 3/3] mfd: pm8008: Add driver for QCOM PM8008 PMIC Guru Das Srinagesh 2021-05-21 0:04 ` [PATCH v4 0/3] Add Qualcomm Technologies, Inc. PM8008 MFD driver Guru Das Srinagesh
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH v4 0/3] Add Qualcomm Technologies, Inc. PM8008 MFD driver' \ /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
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).