From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Naman Jain <quic_namajain@quicinc.com>
Subject: [PATCH v2 0/2] nvmem: qfprom: add Qualcomm SAR2130P support
Date: Sun, 27 Oct 2024 01:42:32 +0300 [thread overview]
Message-ID: <20241027-sar2130p-nvmem-v2-0-743c1271bf2d@linaro.org> (raw)
Pick up a fix from msm-5.x kernels and add compatible for the Qualcomm
SAR2130P platform.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
---
Changes in v2:
- Picked up required patch from QCLinux.
- Link to v1: https://lore.kernel.org/r/20241017-sar2130p-nvmem-v1-1-6cc32789afc6@linaro.org
---
Dmitry Baryshkov (1):
dt-bindings: nvmem: qcom,qfprom: Add SAR2130P compatible
Naman Jain (1):
nvmem: qfprom: Ensure access to qfprom is word aligned
.../devicetree/bindings/nvmem/qcom,qfprom.yaml | 1 +
drivers/nvmem/qfprom.c | 19 ++++++++++++++++---
2 files changed, 17 insertions(+), 3 deletions(-)
---
base-commit: a39230ecf6b3057f5897bc4744a790070cfbe7a8
change-id: 20241017-sar2130p-nvmem-5f856d99bbb7
Best regards,
--
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
next reply other threads:[~2024-10-26 22:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 22:42 Dmitry Baryshkov [this message]
2024-10-26 22:42 ` [PATCH v2 1/2] nvmem: qfprom: Ensure access to qfprom is word aligned Dmitry Baryshkov
2024-12-09 9:55 ` Srinivas Kandagatla
2024-12-09 10:53 ` Dmitry Baryshkov
2024-12-30 7:43 ` Akhil P Oommen
2025-01-04 7:40 ` Dmitry Baryshkov
2025-01-06 19:56 ` Akhil P Oommen
2024-10-26 22:42 ` [PATCH v2 2/2] dt-bindings: nvmem: qcom,qfprom: Add SAR2130P compatible Dmitry Baryshkov
2024-10-27 19:48 ` Krzysztof Kozlowski
2024-11-15 7:59 ` [PATCH v2 0/2] nvmem: qfprom: add Qualcomm SAR2130P support Dmitry Baryshkov
2024-11-30 22:35 ` Dmitry Baryshkov
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=20241027-sar2130p-nvmem-v2-0-743c1271bf2d@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_namajain@quicinc.com \
--cc=robh@kernel.org \
--cc=srinivas.kandagatla@linaro.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).