Re: [PATCH] dt-bindings: nvmem: qfprom: Add Kaanapali compatible

[Akhil P Oommen]

On 3/6/2026 12:10 PM, Jingyi Wang wrote:
> Document compatible string for the QFPROM on Kaanapali platform.
> 
> Signed-off-by: Jingyi Wang <jingyi.wang@xxxxxxxxxxxxxxxx>
> ---
>  Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml b/Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml
> index 839513d4b499..2ab047f2bb69 100644
> --- a/Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml
> +++ b/Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml
> @@ -26,6 +26,7 @@ properties:
>            - qcom,ipq8064-qfprom
>            - qcom,ipq8074-qfprom
>            - qcom,ipq9574-qfprom
> +          - qcom,kaanapali-qfprom

A question to the maintainers.

Do we need a new compatible for every chipset? If there are no KMD
facing differences in the HW, can we use an existing compatible string,
like sm8750's in this case?

The fuse definitions (which map to nvmem cells) will obviously differ
between chipsets, but I am not sure if this alone warrants introducing a
new compatible string.

-Akhil.

>            - qcom,msm8226-qfprom
>            - qcom,msm8916-qfprom
>            - qcom,msm8917-qfprom
> 
> ---
> base-commit: fc7b1a72c6cd5cbbd989c6c32a6486e3e4e3594d
> change-id: 20260305-knp-qfprom-binding-efcff6ea9b7c
> 
> Best regards,