mbox series

[0/5] Add misc support for QDU1000/QRU1000 SoCs

Message ID 20221001030641.29354-1-quic_molvera@quicinc.com
Headers show
Series Add misc support for QDU1000/QRU1000 SoCs | expand

Message

Melody Olvera Oct. 1, 2022, 3:06 a.m. UTC 
This series firmware, SoC, rpmpd, tz-log, and mmc bindings as well as
pmic, rpmpd, and socinfo support for QDU1000 and QRU1000 SoCs.

This patchset is based off of [1] and [2] YAML conversion patches.

The Qualcomm Technologies, Inc. Distributed Unit 1000 and Radio Unit
1000 are new SoCs meant for enabling Open RAN solutions. See more at
https://www.qualcomm.com/content/dam/qcomm-martech/dm-assets/documents/qualcomm_5g_ran_platforms_product_brief.pdf

[1] https://lore.kernel.org/r/20220708090431.30437-1-david@ixit.cz
[2] https://lore.kernel.org/r/20220815100952.23795-8-a39.skl@gmail.com

Melody Olvera (5):
  dt-bindings: firmware: scm: Add QDU1000/QRU1000 compatibles
  dt-bindings: arm: qcom: Document QDU1000/QRU1000 SoCs and boards
  dt-bindings: power: rpmpd: Add QDU1000/QRU1000 to rpmpd binding
  soc: qcom: rpmhpd: Add QDU1000/QRU1000 power domains
  soc: qcom: socinfo: Add QDU1000/QRU1000 and variant IDs

 Documentation/devicetree/bindings/arm/qcom.yaml  | 16 ++++++++++++++++
 .../devicetree/bindings/firmware/qcom,scm.yaml   |  2 ++
 .../devicetree/bindings/power/qcom,rpmpd.yaml    |  2 ++
 drivers/soc/qcom/rpmhpd.c                        | 13 +++++++++++++
 drivers/soc/qcom/socinfo.c                       |  6 ++++++
 include/dt-bindings/power/qcom-rpmpd.h           |  6 ++++++
 6 files changed, 45 insertions(+)


base-commit: 987a926c1d8a40e4256953b04771fbdb63bc7938
prerequisite-patch-id: 54cfdb75ec88e75b31d5c1df0d4a361434334d2b
prerequisite-patch-id: b0108c3601b8ed11cefe4366aa506b2dca364866

Comments

Krzysztof Kozlowski Oct. 1, 2022, 9:34 a.m. UTC | #1 
On 01/10/2022 05:06, Melody Olvera wrote:
> This series firmware, SoC, rpmpd, tz-log, and mmc bindings as well as
> pmic, rpmpd, and socinfo support for QDU1000 and QRU1000 SoCs.
> 
> This patchset is based off of [1] and [2] YAML conversion patches.

All of your patchsets were sent to wrong Bjorn's address. This means
either you based on mainline (which is reasonable but for some reason
address was not fixed in mainline...) or on some older linux-next.

I propose to rebase on recent linux-next, so you will get proper Bjorn's
email.

Best regards,
Krzysztof
Melody Olvera Oct. 4, 2022, 3:27 p.m. UTC | #2 
On 10/1/2022 4:34 AM, Krzysztof Kozlowski wrote:
> On 01/10/2022 05:06, Melody Olvera wrote:
>> This series firmware, SoC, rpmpd, tz-log, and mmc bindings as well as
>> pmic, rpmpd, and socinfo support for QDU1000 and QRU1000 SoCs.
>>
>> This patchset is based off of [1] and [2] YAML conversion patches.
> All of your patchsets were sent to wrong Bjorn's address. This means
> either you based on mainline (which is reasonable but for some reason
> address was not fixed in mainline...) or on some older linux-next.
>
> I propose to rebase on recent linux-next, so you will get proper Bjorn's
> email.
>
> Best regards,
> Krzysztof

Thanks Krzysztof. Yeah I figured that out; will add his most recent email in the next patchset. I was working on the tip of the linux-next stable branch, but does it make more sense to rebase on the master branch of linux-next prior to submitting?

Thanks,

Melody
Melody Olvera Oct. 4, 2022, 4:05 p.m. UTC | #3 
On 10/4/2022 10:27 AM, Melody Olvera wrote:
> On 10/1/2022 4:34 AM, Krzysztof Kozlowski wrote:
>> On 01/10/2022 05:06, Melody Olvera wrote:
>>> This series firmware, SoC, rpmpd, tz-log, and mmc bindings as well as
>>> pmic, rpmpd, and socinfo support for QDU1000 and QRU1000 SoCs.
>>>
>>> This patchset is based off of [1] and [2] YAML conversion patches.
>> All of your patchsets were sent to wrong Bjorn's address. This means
>> either you based on mainline (which is reasonable but for some reason
>> address was not fixed in mainline...) or on some older linux-next.
>>
>> I propose to rebase on recent linux-next, so you will get proper Bjorn's
>> email.
>>
>> Best regards,
>> Krzysztof
> Thanks Krzysztof. Yeah I figured that out; will add his most recent
> email in the next patchset. I was working on the tip of the linux-next
> stable branch, but does it make more sense to rebase on the master
> branch of linux-next prior to submitting? 
> Thanks, Melody 

Fixed formatting.