On Mon, 8 Jun 2026 12:50:40 +0200, Loic Poulain
<[email protected]> said:
> Add support for an NVMEM cell provider for "local-bd-address",
> allowing the Bluetooth stack to retrieve controller's BD address
> from non-volatile storage such as an EEPROM or an eMMC partition.
>
> Reviewed-by: Rob Herring (Arm) <[email protected]>
> Signed-off-by: Loic Poulain <[email protected]>
> ---
>  .../devicetree/bindings/net/bluetooth/qcom,bluetooth-common.yaml | 9 
> +++++++++
>  1 file changed, 9 insertions(+)
>
> diff --git 
> a/Documentation/devicetree/bindings/net/bluetooth/qcom,bluetooth-common.yaml 
> b/Documentation/devicetree/bindings/net/bluetooth/qcom,bluetooth-common.yaml
> index 
> c8e9c55c1afb4c8e05ba2dae41ce2db4194b4a0f..7cb28f30c9af032082f23311f2fc89a32f266f17
>  100644
> --- 
> a/Documentation/devicetree/bindings/net/bluetooth/qcom,bluetooth-common.yaml
> +++ 
> b/Documentation/devicetree/bindings/net/bluetooth/qcom,bluetooth-common.yaml
> @@ -22,4 +22,13 @@ properties:
>      description:
>        boot firmware is incorrectly passing the address in big-endian order
>
> +  nvmem-cells:
> +    maxItems: 1
> +    description:
> +      Nvmem data cell that contains a 6 byte BD address with the most
> +      significant byte first (big-endian).
> +
> +  nvmem-cell-names:
> +    const: local-bd-address
> +
>  additionalProperties: true
>
> --
> 2.34.1
>
>

Reviewed-by: Bartosz Golaszewski <[email protected]>

Reply via email to