From: sashiko-bot@kernel.org
To: "Loic Poulain" <loic.poulain@oss.qualcomm.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v10 03/10] dt-bindings: bluetooth: qcom: Add NVMEM BD address cell
Date: Fri, 07 Aug 2026 14:39:27 +0000 [thread overview]
Message-ID: <20260807143928.301141F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260806-block-as-nvmem-v10-3-be598b2a5606@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Missing C implementation for Bluetooth NVMEM cell consumption.
--
--- Patch [3]: [PATCH v10 03/10] dt-bindings: bluetooth: qcom: Add NVMEM BD address cell ---
commit fd2db3f3069a2b6bb144aea20efff2a8e20aaf2a
Author: Loic Poulain <loic.poulain@oss.qualcomm.com>
dt-bindings: bluetooth: qcom: Add NVMEM BD address cell
This commit adds support for an NVMEM cell provider for local-bd-address
in the Qualcomm Bluetooth device tree binding. It intends to allow the
Bluetooth stack to retrieve the controller's BD address from non-volatile
storage.
> diff --git a/Documentation/devicetree/bindings/net/bluetooth/qcom,bluetooth-common.yaml b/Documentation/devicetree/bindings/net/bluetooth/qcom,bluetooth-common.yaml
> --- 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
[Severity: Medium]
Is the C code implementation to read this cell missing from this patch series?
The commit message mentions this allows the Bluetooth stack to retrieve the
controller's BD address from non-volatile storage. However, unlike the
networking stack (which natively resolves mac-address NVMEM cells via
of_get_mac_address_nvmem()), the Bluetooth stack currently only reads the
static local-bd-address firmware node property via
fwnode_property_read_u8_array() in net/bluetooth/hci_sync.c.
Does there need to be a corresponding patch that implements nvmem_cell_get()
for local-bd-address in the Bluetooth core or Qualcomm drivers for this
binding to actually be functional?
> + 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
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260806-block-as-nvmem-v10-0-be598b2a5606@oss.qualcomm.com?part=3
next prev parent reply other threads:[~2026-08-07 14:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 14:38 [PATCH v10 00/10] Support for block device NVMEM providers Loic Poulain
2026-08-06 14:38 ` [PATCH v10 01/10] dt-bindings: mmc: Document fixed-layout NVMEM provider support Loic Poulain
2026-08-06 14:38 ` [PATCH v10 02/10] dt-bindings: net: wireless: qcom,ath10k: Document NVMEM cells Loic Poulain
2026-08-06 14:38 ` [PATCH v10 03/10] dt-bindings: bluetooth: qcom: Add NVMEM BD address cell Loic Poulain
2026-08-07 14:39 ` sashiko-bot [this message]
2026-08-06 14:38 ` [PATCH v10 04/10] nvmem: layouts: Support fixed-layout as the nvmem device node itself Loic Poulain
2026-08-07 14:39 ` sashiko-bot
2026-08-06 14:38 ` [PATCH v10 05/10] block: partitions: of: Attach partition fwnode to the block device Loic Poulain
2026-08-07 14:39 ` sashiko-bot
2026-08-06 14:38 ` [PATCH v10 06/10] block: implement NVMEM provider Loic Poulain
2026-08-07 14:39 ` sashiko-bot
2026-08-06 14:38 ` [PATCH v10 07/10] net: of_net: Add of_get_nvmem_eui48() helper for EUI-48 lookup Loic Poulain
2026-08-06 14:38 ` [PATCH v10 08/10] Bluetooth: hci_sync: Add NVMEM-backed BD address retrieval Loic Poulain
2026-08-07 14:39 ` sashiko-bot
2026-08-06 14:38 ` [PATCH v10 09/10] Bluetooth: qca: Set NVMEM BD address quirks when address is invalid Loic Poulain
2026-08-06 14:38 ` [PATCH v10 10/10] arm64: dts: qcom: arduino-imola: Add NVMEM layout for WiFi/BT Loic Poulain
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=20260807143928.301141F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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