This series contains patches to update rpmh-regulator driver and
dt-bindings for supporting the PMIC voltage regulators present on the
boards with Qualcomm's next gen compute SoC - Glymur.

Device tree changes aren't part of this series and will be posted
separately after the official announcement of the Glymur SoC.

Signed-off-by: Kamal Wadhwa <kamal.wadhwa@oss.qualcomm.com>
---
Changes in v3:
- Added more details in pmic-id dt binding's commit message to clearly
  explain about the limitation in existing CMD-DB names and why the
  new format has been added and how this changes the pmic-id
  interpretation in code
- Fixed the issue reported-by the `kernel test robot <lkp@intel.com>`
  in patch [3/4] code comments to close:
  https://lore.kernel.org/oe-kbuild-all/202509171822.oRjF64pS-lkp@intel.com/
- Link to v2: https://lore.kernel.org/r/20250916-glymur-rpmh-regulator-driver-v2-0-c6593ff9b4be@oss.qualcomm.com

Changes in v2:
- Updated pmic-id dt binding's change commit message to elaborate `why` the
  dt-binding change is needed
- Updated commit message for driver change related to new resource name patch
  to clarify that `resource name` refers to `cmd-db resource names`.
- Link to v1: https://lore.kernel.org/r/20250916-glymur-rpmh-regulator-driver-v1-0-bb9b00e93a61@oss.qualcomm.com

---
Kamal Wadhwa (4):
      dt-bindings: rpmh-regulator : Add compatibles for PMH01XX & PMCX0102
      dt-bindings: rpmh-regulator: Update pmic-id DT prop info for new CMD-DB
      regulator: rpmh-regulator: Add support for new resource name format
      regulator: rpmh-regulator: Add RPMH regulator support for Glymur

 .../bindings/regulator/qcom,rpmh-regulator.yaml    |   39 +-
 drivers/regulator/qcom-rpmh-regulator.c            | 1323 ++++++++++++--------
 2 files changed, 812 insertions(+), 550 deletions(-)
---
base-commit: c3067c2c38316c3ef013636c93daa285ee6aaa2e
change-id: 20250916-glymur-rpmh-regulator-driver-80c9543cdd6e

Best regards,
-- 
Kamal Wadhwa <kamal.wadhwa@oss.qualcomm.com>

On Thu, 18 Sep 2025 14:57:00 +0530, Kamal Wadhwa wrote:
> This series contains patches to update rpmh-regulator driver and
> dt-bindings for supporting the PMIC voltage regulators present on the
> boards with Qualcomm's next gen compute SoC - Glymur.
> 
> Device tree changes aren't part of this series and will be posted
> separately after the official announcement of the Glymur SoC.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/4] dt-bindings: rpmh-regulator : Add compatibles for PMH01XX & PMCX0102
      commit: 835dfb12fc389f36eb007657f163bd1c539dcd45
[2/4] dt-bindings: rpmh-regulator: Update pmic-id DT prop info for new CMD-DB
      commit: 1356c98ef911e14ccfaf374800840ce5bdcb3bbd
[3/4] regulator: rpmh-regulator: Add support for new resource name format
      commit: 6a8cdef7dc2a4c0dbde3f7d7100b3d99712a766b
[4/4] regulator: rpmh-regulator: Add RPMH regulator support for Glymur
      commit: 65efe5404d151767653c7b7dd39bd2e7ad532c2d

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark

On Thu, Sep 18, 2025 at 02:57:00PM +0530, Kamal Wadhwa wrote:
> This series contains patches to update rpmh-regulator driver and
> dt-bindings for supporting the PMIC voltage regulators present on the
> boards with Qualcomm's next gen compute SoC - Glymur.

Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resemble what they're doing.
There's no need to resubmit to fix this alone.