On Thu, Jun 25, 2026 at 06:10:05PM +0400, George Moussalem wrote: > Document the M0 Bluetooth Subsystem remote processor core found in the > Qualcomm IPQ5018 SoC. Firmware loaded is authenticated via TrustZone. > The firmware running on the M0 core provides bluetooth functionality. > > Signed-off-by: George Moussalem <[email protected]> > --- > .../bindings/remoteproc/qcom,m0-btss-pil.yaml | 72 > ++++++++++++++++++++++ > 1 file changed, 72 insertions(+) > > diff --git > a/Documentation/devicetree/bindings/remoteproc/qcom,m0-btss-pil.yaml > b/Documentation/devicetree/bindings/remoteproc/qcom,m0-btss-pil.yaml > new file mode 100644 > index 000000000000..397bb6815d71 > --- /dev/null > +++ b/Documentation/devicetree/bindings/remoteproc/qcom,m0-btss-pil.yaml
Use compatible as filename. > @@ -0,0 +1,72 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/remoteproc/qcom,m0-btss-pil.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Qualcomm M0 BTSS Peripheral Image Loader > + > +maintainers: > + - George Moussalem <[email protected]> > + > +description: > + Qualcomm M0 BTSS Peripheral Secure Image Loader loads firmware and powers > up > + the M0 BTSS remote processor core on the Qualcomm IPQ5018 SoC. > + > +properties: > + compatible: > + enum: > + - qcom,ipq5018-btss-pil > + > + firmware-name: > + maxItems: 1 > + description: Firmware name for the M0 Bluetooth Subsystem core You can drop description, pretty obvious. > + > + clocks: > + items: > + - description: M0 BTSS low power oscillator clock > + > + clock-names: > + items: > + - const: btss_lpo_clk Just "lpo" > + > + memory-region: > + items: > + - description: M0 BTSS reserved memory carveout > + > + resets: > + items: > + - description: M0 BTSS reset > + > + reset-names: > + items: > + - const: btss_reset Drop names. Using block name as input name is not really useful. No supplies? no address space? How do you actually trigger remoteproc startup? > + > +required: > + - compatible > + - firmware-name > + - clocks > + - clock-names > + - resets > + - reset-names > + - memory-region > + > +additionalProperties: false Best regards, Krzysztof
