From: Nick Li <nick.li@foursemi.com>
This patch adds bindings for FourSemi FS2104/5S audio amplifiers
which can support both I2S and I2C interface.
Signed-off-by: Nick Li <nick.li@foursemi.com>
---
.../bindings/sound/foursemi,fs210x.yaml | 95 +++++++++++++++++++
1 file changed, 95 insertions(+)
create mode 100644 Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml
diff --git a/Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml b/Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml
new file mode 100644
index 000000000..3a1aba9b8
--- /dev/null
+++ b/Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml
@@ -0,0 +1,95 @@
+# SPDX-License-Identifier: GPL-2.0-only
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/sound/foursemi,fs210x.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: FourSemi FS2104/5S Digital Audio Amplifier
+
+maintainers:
+ - Nick <nick.li@foursemi.com>
+
+description: |
+ The FS2104 is a 15W Inductor-Less, Stereo, Closed-Loop,
+ Digital Input Class-D Power Amplifier with Enhanced Signal Processing.
+ The FS2105S is a 30W Inductor-Less, Stereo, Closed-Loop,
+ Digital Input Class-D Power Amplifier with Enhanced Signal Processing.
+
+properties:
+ compatible:
+ enum:
+ - foursemi,fs2104
+ - foursemi,fs2105s
+
+ reg:
+ maxItems: 1
+ description: |
+ I2C address of the amplifier. Refer to datasheet for possible values:
+ 0x68/0x69/0x6A/0x6B
+
+ clocks:
+ items:
+ - description: The clock of I2S BCLK
+
+ clock-names:
+ items:
+ - const: bclk
+
+ '#sound-dai-cells':
+ const: 0
+
+ pvdd-supply:
+ description: |
+ Regulator for power supply(PVDD in datasheet).
+
+ dvdd-supply:
+ description: |
+ Regulator for digital supply(DVDD in datasheet).
+
+ sdz-gpios:
+ maxItems: 1
+ description: |
+ SDZ(Shut Down) pin is active low, it will power down the chip,
+ and then reset the chip to shut down state.
+
+ fs,fwm-name:
+ description: |
+ The name of firmware that should be loaded for this
+ instance. The firmware is gernerated by FourSemi's tuning tool.
+ $ref: /schemas/types.yaml#/definitions/string
+
+ fs,dai-name:
+ description: |
+ The name of FS210x DAI, it can be set different name when
+ there are multiple FS210x devices in the system.
+ $ref: /schemas/types.yaml#/definitions/string
+
+required:
+ - compatible
+ - reg
+ - sdz-gpios
+ - fs,fwm-name
+ - '#sound-dai-cells'
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/gpio/gpio.h>
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ audio-codec@68 {
+ compatible = "foursemi,fs2105s";
+ reg = <0x68>;
+ pvdd-supply = <&pvdd_supply>;
+ dvdd-supply = <&dvdd_supply>;
+ sdz-gpios = <&gpio 18 GPIO_ACTIVE_LOW>;
+ pinctrl-names = "default";
+ pinctrl-0 = <&fs210x_pins_default>;
+ fs,fwm-name = "fs2105s-btl-2p0-0s.bin";
+ clocks = <&clocks 18>;
+ clock-names = "bclk";
+ #sound-dai-cells = <0>;
+ };
+ };
--
2.39.5
On Thu, Jul 03, 2025 at 11:56:38AM +0800, Nick wrote: > From: Nick Li <nick.li@foursemi.com> > > This patch adds bindings for FourSemi FS2104/5S audio amplifiers > which can support both I2S and I2C interface. > > Signed-off-by: Nick Li <nick.li@foursemi.com> > --- > .../bindings/sound/foursemi,fs210x.yaml | 95 +++++++++++++++++++ > 1 file changed, 95 insertions(+) > create mode 100644 Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml > > diff --git a/Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml b/Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml > new file mode 100644 > index 000000000..3a1aba9b8 > --- /dev/null > +++ b/Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml > @@ -0,0 +1,95 @@ > +# SPDX-License-Identifier: GPL-2.0-only Please run scripts/checkpatch.pl on the patches and fix reported warnings. After that, run also 'scripts/checkpatch.pl --strict' on the patches and (probably) fix more warnings. Some warnings can be ignored, especially from --strict run, but the code here looks like it needs a fix. Feel free to get in touch if the warning is not clear. Best regards, Krzysztof
On Thu, Jul 03, 2025 at 09:10:38AM +0200, Krzysztof Kozlowski wrote: > On Thu, Jul 03, 2025 at 11:56:38AM +0800, Nick wrote: > > From: Nick Li <nick.li@foursemi.com> > > > > This patch adds bindings for FourSemi FS2104/5S audio amplifiers > > which can support both I2S and I2C interface. > > > > Signed-off-by: Nick Li <nick.li@foursemi.com> > > --- > > .../bindings/sound/foursemi,fs210x.yaml | 95 +++++++++++++++++++ > > 1 file changed, 95 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml > > > > diff --git a/Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml b/Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml > > new file mode 100644 > > index 000000000..3a1aba9b8 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml > > @@ -0,0 +1,95 @@ > > +# SPDX-License-Identifier: GPL-2.0-only > > Please run scripts/checkpatch.pl on the patches and fix reported > warnings. After that, run also 'scripts/checkpatch.pl --strict' on the > patches and (probably) fix more warnings. Some warnings can be ignored, > especially from --strict run, but the code here looks like it needs a > fix. Feel free to get in touch if the warning is not clear. OK, I will check the patches with option --strict, and fix the warnings/errors in next version. Thanks. Best regards, Nick > > Best regards, > Krzysztof > >
On 03/07/2025 09:10, Krzysztof Kozlowski wrote: > On Thu, Jul 03, 2025 at 11:56:38AM +0800, Nick wrote: >> From: Nick Li <nick.li@foursemi.com> >> >> This patch adds bindings for FourSemi FS2104/5S audio amplifiers >> which can support both I2S and I2C interface. >> >> Signed-off-by: Nick Li <nick.li@foursemi.com> >> --- >> .../bindings/sound/foursemi,fs210x.yaml | 95 +++++++++++++++++++ >> 1 file changed, 95 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml >> >> diff --git a/Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml b/Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml >> new file mode 100644 >> index 000000000..3a1aba9b8 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml >> @@ -0,0 +1,95 @@ >> +# SPDX-License-Identifier: GPL-2.0-only > > Please run scripts/checkpatch.pl on the patches and fix reported > warnings. After that, run also 'scripts/checkpatch.pl --strict' on the > patches and (probably) fix more warnings. Some warnings can be ignored, > especially from --strict run, but the code here looks like it needs a > fix. Feel free to get in touch if the warning is not clear. One more thing: Drop "dt-bindings for" from subject. See also: https://elixir.bootlin.com/linux/v6.7-rc8/source/Documentation/devicetree/bindings/submitting-patches.rst#L18 ... and that was my third email today... I apologize I did not send these as one review email, that's not really professional from my side but somehow coffee did not work good this morning. Best regards, Krzysztof
On Thu, Jul 03, 2025 at 09:15:36AM +0200, Krzysztof Kozlowski wrote: > On 03/07/2025 09:10, Krzysztof Kozlowski wrote: > > On Thu, Jul 03, 2025 at 11:56:38AM +0800, Nick wrote: > >> From: Nick Li <nick.li@foursemi.com> > >> > >> This patch adds bindings for FourSemi FS2104/5S audio amplifiers > >> which can support both I2S and I2C interface. > >> > >> Signed-off-by: Nick Li <nick.li@foursemi.com> > >> --- > >> .../bindings/sound/foursemi,fs210x.yaml | 95 +++++++++++++++++++ > >> 1 file changed, 95 insertions(+) > >> create mode 100644 Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml > >> > >> diff --git a/Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml b/Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml > >> new file mode 100644 > >> index 000000000..3a1aba9b8 > >> --- /dev/null > >> +++ b/Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml > >> @@ -0,0 +1,95 @@ > >> +# SPDX-License-Identifier: GPL-2.0-only > > > > Please run scripts/checkpatch.pl on the patches and fix reported > > warnings. After that, run also 'scripts/checkpatch.pl --strict' on the > > patches and (probably) fix more warnings. Some warnings can be ignored, > > especially from --strict run, but the code here looks like it needs a > > fix. Feel free to get in touch if the warning is not clear. > > > One more thing: Drop "dt-bindings for" from subject. > See also: > https://elixir.bootlin.com/linux/v6.7-rc8/source/Documentation/devicetree/bindings/submitting-patches.rst#L18 OK, update it in next version. > > > ... and that was my third email today... I apologize I did not send > these as one review email, that's not really professional from my side > but somehow coffee did not work good this morning. > Thank you for taking your valuable time to review the code. Best regards, Nick > Best regards, > Krzysztof >
On 03/07/2025 05:56, Nick wrote: > From: Nick Li <nick.li@foursemi.com> > > This patch adds bindings for FourSemi FS2104/5S audio amplifiers > which can support both I2S and I2C interface. > > Signed-off-by: Nick Li <nick.li@foursemi.com> Your patches are not correctly ordered. Vendor prefix is supposed to be before is being used. Bindings are before their users. > --- > .../bindings/sound/foursemi,fs210x.yaml | 95 +++++++++++++++++++ > 1 file changed, 95 insertions(+) > create mode 100644 Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml > > diff --git a/Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml b/Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml > new file mode 100644 > index 000000000..3a1aba9b8 > --- /dev/null > +++ b/Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml Choose one compatible as filename. > @@ -0,0 +1,95 @@ > +# SPDX-License-Identifier: GPL-2.0-only > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/sound/foursemi,fs210x.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: FourSemi FS2104/5S Digital Audio Amplifier > + > +maintainers: > + - Nick <nick.li@foursemi.com> > + > +description: | > + The FS2104 is a 15W Inductor-Less, Stereo, Closed-Loop, > + Digital Input Class-D Power Amplifier with Enhanced Signal Processing. > + The FS2105S is a 30W Inductor-Less, Stereo, Closed-Loop, > + Digital Input Class-D Power Amplifier with Enhanced Signal Processing. > + > +properties: > + compatible: > + enum: > + - foursemi,fs2104 > + - foursemi,fs2105s Your driver suggests these are compatible, so express that with fallback. > + > + reg: > + maxItems: 1 > + description: | Do not need '|' unless you need to preserve formatting. > + I2C address of the amplifier. Refer to datasheet for possible values: > + 0x68/0x69/0x6A/0x6B > + > + clocks: > + items: > + - description: The clock of I2S BCLK > + > + clock-names: > + items: > + - const: bclk > + > + '#sound-dai-cells': > + const: 0 > + > + pvdd-supply: > + description: | Do not need '|' unless you need to preserve formatting. > + Regulator for power supply(PVDD in datasheet). > + > + dvdd-supply: > + description: | Do not need '|' unless you need to preserve formatting. > + Regulator for digital supply(DVDD in datasheet). > + > + sdz-gpios: Use standard properties - see gpio-consumer-common > + maxItems: 1 > + description: | > + SDZ(Shut Down) pin is active low, it will power down the chip, > + and then reset the chip to shut down state. > + > + fs,fwm-name: No, use standard properties (see writing bindings) > + description: | > + The name of firmware that should be loaded for this > + instance. The firmware is gernerated by FourSemi's tuning tool. > + $ref: /schemas/types.yaml#/definitions/string > + > + fs,dai-name: No, it's already in dai-common > + description: | > + The name of FS210x DAI, it can be set different name when > + there are multiple FS210x devices in the system. > + $ref: /schemas/types.yaml#/definitions/string > + > +required: > + - compatible > + - reg > + - sdz-gpios > + - fs,fwm-name > + - '#sound-dai-cells' > + Missing ref to dai common > +additionalProperties: false And this should be unevaluatedProperties instead Best regards, Krzysztof
On Thu, Jul 03, 2025 at 08:36:42AM +0200, Krzysztof Kozlowski wrote: > On 03/07/2025 05:56, Nick wrote: > > From: Nick Li <nick.li@foursemi.com> > > > > This patch adds bindings for FourSemi FS2104/5S audio amplifiers > > which can support both I2S and I2C interface. > > > > Signed-off-by: Nick Li <nick.li@foursemi.com> > > Your patches are not correctly ordered. Vendor prefix is supposed to be > before is being used. Bindings are before their users. OK, I will update the orders of patches in next version. > > > --- > > .../bindings/sound/foursemi,fs210x.yaml | 95 +++++++++++++++++++ > > 1 file changed, 95 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml > > > > diff --git a/Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml b/Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml > > new file mode 100644 > > index 000000000..3a1aba9b8 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml > > Choose one compatible as filename. OK, I will update the file name to foursemi,fs2105s.yaml > > > @@ -0,0 +1,95 @@ > > +# SPDX-License-Identifier: GPL-2.0-only > > +%YAML 1.2 > > +--- > > +$id: http://devicetree.org/schemas/sound/foursemi,fs210x.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: FourSemi FS2104/5S Digital Audio Amplifier > > + > > +maintainers: > > + - Nick <nick.li@foursemi.com> > > + > > +description: | > > + The FS2104 is a 15W Inductor-Less, Stereo, Closed-Loop, > > + Digital Input Class-D Power Amplifier with Enhanced Signal Processing. > > + The FS2105S is a 30W Inductor-Less, Stereo, Closed-Loop, > > + Digital Input Class-D Power Amplifier with Enhanced Signal Processing. > > + > > +properties: > > + compatible: > > + enum: > > + - foursemi,fs2104 > > + - foursemi,fs2105s > > Your driver suggests these are compatible, so express that with fallback. OK, I will update these code to: oneOf: - items: ... - enum: ... > > > + > > + reg: > > + maxItems: 1 > > + description: | > > Do not need '|' unless you need to preserve formatting. OK, I will delete it in next version. > > > + I2C address of the amplifier. Refer to datasheet for possible values: > > + 0x68/0x69/0x6A/0x6B > > + > > + clocks: > > + items: > > + - description: The clock of I2S BCLK > > + > > + clock-names: > > + items: > > + - const: bclk > > + > > + '#sound-dai-cells': > > + const: 0 > > + > > + pvdd-supply: > > + description: | > > Do not need '|' unless you need to preserve formatting. OK, I will delete it in next version. > > > > + Regulator for power supply(PVDD in datasheet). > > + > > + dvdd-supply: > > + description: | > > Do not need '|' unless you need to preserve formatting. OK, I will delete it. > > > + Regulator for digital supply(DVDD in datasheet). > > + > > + sdz-gpios: > > Use standard properties - see gpio-consumer-common OK, I will update this property to reset-gpios, and update the driver. > > > + maxItems: 1 > > + description: | > > + SDZ(Shut Down) pin is active low, it will power down the chip, > > + and then reset the chip to shut down state. > > + > > + fs,fwm-name: > > No, use standard properties (see writing bindings) OK, I will update this property to firmware-name, and update the driver. > > > + description: | > > + The name of firmware that should be loaded for this > > + instance. The firmware is gernerated by FourSemi's tuning tool. > > + $ref: /schemas/types.yaml#/definitions/string > > + > > + fs,dai-name: > > No, it's already in dai-common OK, delete it in next version, and update the driver. > > > + description: | > > + The name of FS210x DAI, it can be set different name when > > + there are multiple FS210x devices in the system. > > + $ref: /schemas/types.yaml#/definitions/string > > + > > +required: > > + - compatible > > + - reg > > + - sdz-gpios > > + - fs,fwm-name > > + - '#sound-dai-cells' > > + > > Missing ref to dai common OK, reference will be added: allOf: - $ref: dai-common.yaml# > > > +additionalProperties: false > > And this should be unevaluatedProperties instead OK, I will update it to: unevaluatedProperties: false Thanks for your patient response very mush. Best regards, Nick > > > Best regards, > Krzysztof >
On Thu, 03 Jul 2025 11:56:38 +0800, Nick wrote: > From: Nick Li <nick.li@foursemi.com> > > This patch adds bindings for FourSemi FS2104/5S audio amplifiers > which can support both I2S and I2C interface. > > Signed-off-by: Nick Li <nick.li@foursemi.com> > --- > .../bindings/sound/foursemi,fs210x.yaml | 95 +++++++++++++++++++ > 1 file changed, 95 insertions(+) > create mode 100644 Documentation/devicetree/bindings/sound/foursemi,fs210x.yaml > My bot found errors running 'make dt_binding_check' on your patch: yamllint warnings/errors: dtschema/dtc warnings/errors: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/sound/foursemi,fs210x.example.dtb: audio-codec@68 (foursemi,fs2105s): 'fs,fwm-name' does not match any of the regexes: '^#.*', '^(at25|bm|devbus|dmacap|dsa|exynos|fsi[ab]|gpio-fan|gpio-key|gpio|gpmc|hdmi|i2c-gpio),.*', '^(keypad|m25p|max8952|max8997|max8998|mpmc),.*', '^(pciclass|pinctrl-single|#pinctrl-single|PowerPC),.*', '^(pl022|pxa-mmc|rcar_sound|rotary-encoder|s5m8767|sdhci),.*', '^(simple-audio-card|st-plgpio|st-spics|ts),.*', '^100ask,.*', '^70mai,.*', '^8dev,.*', '^GEFanuc,.*', '^IBM,.*', '^ORCL,.*', '^SUNW,.*', '^[a-zA-Z0-9#_][a-zA-Z0-9+\\-._@]{0,63}$', '^[a-zA-Z0-9+\\-._]*@[0-9a-zA-Z,]*$', '^abb,.*', '^abilis,.*', '^abracon,.*', '^abt,.*', '^acbel,.*', '^acelink,.*', '^acer,.*', '^acme,.*', '^actions,.*', '^active-semi,.*', '^ad,.*', '^adafruit,.*', '^adapteva,.*', '^adaptrum,.*', '^adh,.*', '^adi,.*', '^adieng,.*', '^admatec,.*', '^advantech,.*', '^aeroflexgaisler,.*', '^aesop,.*', '^airoha,.*', '^al,.*', '^alcatel,.*', '^aldec,.*', '^alfa-network,.*', '^allegro,.*', '^allegromicro,.*', '^alliedvision,.*', '^allo,.*', '^allwinner,.*', '^alphascale,.*', '^alps,.*', '^alt,.*', '^altr,.*', '^amarula,.*', '^amazon,.*', '^amcc,.*', '^amd,.*', '^amediatech,.*', '^amlogic,.*', '^ampere,.*', '^amphenol,.*', '^ampire,.*', '^ams,.*', '^amstaos,.*', '^analogix,.*', '^anbernic,.*', '^andestech,.*', '^anvo,.*', '^aoly,.*', '^aosong,.*', '^apm,.*', '^apple,.*', '^aptina,.*', '^arasan,.*', '^archermind,.*', '^arcom,.*', '^arctic,.*', '^arcx,.*', '^argon40,.*', '^ariaboard,.*', '^aries,.*', '^arm,.*', '^armadeus,.*', '^armsom,.*', '^arrow,.*', '^artesyn,.*', '^asahi-kasei,.*', '^asc,.*', '^asix,.*', '^aspeed,.*', '^asrock,.*', '^asteralabs,.*', '^asus,.*', '^atheros,.*', '^atlas,.*', '^atmel,.*', '^auo,.*', '^auvidea,.*', '^avago,.*', '^avia,.*', '^avic,.*', '^avnet,.*', '^awinic,.*', '^axentia,.*', '^axis,.*', '^azoteq,.*', '^azw,.*', '^baikal,.*', '^bananapi,.*', '^beacon,.*', '^beagle,.*', '^belling,.*', '^bhf,.*', '^bigtreetech,.*', '^bitmain,.*', '^blaize,.*', '^blutek,.*', '^boe,.*', '^bosch,.*', '^boundary,.*', '^brcm,.*', '^broadmobi,.*', '^bsh,.*', '^bticino,.*', '^buffalo,.*', '^bur,.*', '^bytedance,.*', '^calamp,.*', '^calao,.*', '^calaosystems,.*', '^calxeda,.*', '^cameo,.*', '^canaan,.*', '^caninos,.*', '^capella,.*', '^cascoda,.*', '^catalyst,.*', '^cavium,.*', '^cct,.*', '^cdns,.*', '^cdtech,.*', '^cellwise,.*', '^ceva,.*', '^chargebyte,.*', '^checkpoint,.*', '^chefree,.*', '^chipidea,.*', '^chipone,.*', '^chipspark,.*', '^chongzhou,.*', '^chrontel,.*', '^chrp,.*', '^chunghwa,.*', '^chuwi,.*', '^ciaa,.*', '^cirrus,.*', '^cisco,.*', '^clockwork,.*', '^cloos,.*', '^cloudengines,.*', '^cnm,.*', '^cnxt,.*', '^colorfly,.*', '^compulab,.*', '^comvetia,.*', '^congatec,.*', '^coolpi,.*', '^coreriver,.*', '^corpro,.*', '^cortina,.*', '^cosmic,.*', '^crane,.*', '^creative,.*', '^crystalfontz,.*', '^csky,.*', '^csot,.*', '^csq,.*', '^ctera,.*', '^ctu,.*', '^cubietech,.*', '^cudy,.*', '^cui,.*', '^cypress,.*', '^cyx,.*', '^cznic,.*', '^dallas,.*', '^dataimage,.*', '^davicom,.*', '^deepcomputing,.*', '^dell,.*', '^delta,.*', '^densitron,.*', '^denx,.*', '^devantech,.*', '^dfi,.*', '^dfrobot,.*', '^dh,.*', '^difrnce,.*', '^digi,.*', '^digilent,.*', '^dimonoff,.*', '^diodes,.*', '^dioo,.*', '^djn,.*', '^dlc,.*', '^dlg,.*', '^dlink,.*', '^dmo,.*', '^domintech,.*', '^dongwoon,.*', '^dptechnics,.*', '^dragino,.*', '^dream,.*', '^ds,.*', '^dserve,.*', '^dynaimage,.*', '^ea,.*', '^ebang,.*', '^ebbg,.*', '^ebs-systart,.*', '^ebv,.*', '^eckelmann,.*', '^econet,.*', '^edgeble,.*', '^edimax,.*', '^edt,.*', '^ees,.*', '^eeti,.*', '^einfochips,.*', '^eink,.*', '^elan,.*', '^element14,.*', '^elgin,.*', '^elida,.*', '^elimo,.*', '^elpida,.*', '^embedfire,.*', '^embest,.*', '^emcraft,.*', '^emlid,.*', '^emmicro,.*', '^empire-electronix,.*', '^emtrion,.*', '^enclustra,.*', '^endless,.*', '^ene,.*', '^energymicro,.*', '^engicam,.*', '^engleder,.*', '^epcos,.*', '^epfl,.*', '^epson,.*', '^esp,.*', '^est,.*', '^ettus,.*', '^eukrea,.*', '^everest,.*', '^everspin,.*', '^evervision,.*', '^exar,.*', '^excito,.*', '^exegin,.*', '^ezchip,.*', '^facebook,.*', '^fairchild,.*', '^fairphone,.*', '^faraday,.*', '^fascontek,.*', '^fastrax,.*', '^fcs,.*', '^feixin,.*', '^feiyang,.*', '^fii,.*', '^firefly,.*', '^focaltech,.*', '^forlinx,.*', '^freebox,.*', '^freecom,.*', '^frida,.*', '^friendlyarm,.*', '^fsl,.*', '^fujitsu,.*', '^fxtec,.*', '^galaxycore,.*', '^gameforce,.*', '^gardena,.*', '^gateway,.*', '^gateworks,.*', '^gcw,.*', '^ge,.*', '^geekbuying,.*', '^gef,.*', '^gehc,.*', '^gemei,.*', '^gemtek,.*', '^genesys,.*', '^genexis,.*', '^geniatech,.*', '^giantec,.*', '^giantplus,.*', '^glinet,.*', '^globalscale,.*', '^globaltop,.*', '^gmt,.*', '^gocontroll,.*', '^goldelico,.*', '^goodix,.*', '^google,.*', '^goramo,.*', '^gplus,.*', '^grinn,.*', '^grmn,.*', '^gumstix,.*', '^gw,.*', '^hannstar,.*', '^haochuangyi,.*', '^haoyu,.*', '^hardkernel,.*', '^hechuang,.*', '^hideep,.*', '^himax,.*', '^hirschmann,.*', '^hisi,.*', '^hisilicon,.*', '^hit,.*', '^hitex,.*', '^holt,.*', '^holtek,.*', '^honestar,.*', '^honeywell,.*', '^hoperf,.*', '^hoperun,.*', '^hp,.*', '^hpe,.*', '^hsg,.*', '^htc,.*', '^huawei,.*', '^hugsun,.*', '^huiling,.*', '^hwacom,.*', '^hxt,.*', '^hycon,.*', '^hydis,.*', '^hynitron,.*', '^hynix,.*', '^hyundai,.*', '^i2se,.*', '^ibm,.*', '^icplus,.*', '^idt,.*', '^iei,.*', '^ifi,.*', '^ilitek,.*', '^imagis,.*', '^img,.*', '^imi,.*', '^inanbo,.*', '^incircuit,.*', '^indiedroid,.*', '^inet-tek,.*', '^infineon,.*', '^inforce,.*', '^ingenic,.*', '^ingrasys,.*', '^injoinic,.*', '^innocomm,.*', '^innolux,.*', '^inside-secure,.*', '^insignal,.*', '^inspur,.*', '^intel,.*', '^intercontrol,.*', '^invensense,.*', '^inventec,.*', '^inversepath,.*', '^iom,.*', '^irondevice,.*', '^isee,.*', '^isil,.*', '^issi,.*', '^ite,.*', '^itead,.*', '^itian,.*', '^ivo,.*', '^iwave,.*', '^jadard,.*', '^jasonic,.*', '^jdi,.*', '^jedec,.*', '^jenson,.*', '^jesurun,.*', '^jethome,.*', '^jianda,.*', '^jide,.*', '^joz,.*', '^kam,.*', '^karo,.*', '^keithkoep,.*', '^keymile,.*', '^khadas,.*', '^kiebackpeter,.*', '^kinetic,.*', '^kingdisplay,.*', '^kingnovel,.*', '^kionix,.*', '^kobo,.*', '^kobol,.*', '^koe,.*', '^kontron,.*', '^kosagi,.*', '^kvg,.*', '^kyo,.*', '^lacie,.*', '^laird,.*', '^lamobo,.*', '^lantiq,.*', '^lattice,.*', '^lckfb,.*', '^lctech,.*', '^leadtek,.*', '^leez,.*', '^lego,.*', '^lemaker,.*', '^lenovo,.*', '^lg,.*', '^lgphilips,.*', '^libretech,.*', '^licheepi,.*', '^linaro,.*', '^lincolntech,.*', '^lineartechnology,.*', '^linksprite,.*', '^linksys,.*', '^linutronix,.*', '^linux,.*', '^linx,.*', '^liontron,.*', '^liteon,.*', '^litex,.*', '^lltc,.*', '^logicpd,.*', '^logictechno,.*', '^longcheer,.*', '^lontium,.*', '^loongmasses,.*', '^loongson,.*', '^lsi,.*', '^luckfox,.*', '^lunzn,.*', '^luxul,.*', '^lwn,.*', '^lxa,.*', '^m5stack,.*', '^macnica,.*', '^mantix,.*', '^mapleboard,.*', '^marantec,.*', '^marvell,.*', '^maxbotix,.*', '^maxim,.*', '^maxlinear,.*', '^mbvl,.*', '^mcube,.*', '^meas,.*', '^mecer,.*', '^mediatek,.*', '^megachips,.*', '^mele,.*', '^melexis,.*', '^melfas,.*', '^mellanox,.*', '^memsensing,.*', '^memsic,.*', '^menlo,.*', '^mentor,.*', '^meraki,.*', '^merrii,.*', '^methode,.*', '^micrel,.*', '^microchip,.*', '^microcrystal,.*', '^micron,.*', '^microsoft,.*', '^microsys,.*', '^microtips,.*', '^mikroe,.*', '^mikrotik,.*', '^milkv,.*', '^miniand,.*', '^minix,.*', '^mips,.*', '^miramems,.*', '^mitsubishi,.*', '^mitsumi,.*', '^mixel,.*', '^miyoo,.*', '^mntre,.*', '^mobileye,.*', '^modtronix,.*', '^moortec,.*', '^mosaixtech,.*', '^motorcomm,.*', '^motorola,.*', '^moxa,.*', '^mpl,.*', '^mps,.*', '^mqmaker,.*', '^mrvl,.*', '^mscc,.*', '^msi,.*', '^mstar,.*', '^mti,.*', '^multi-inno,.*', '^mundoreader,.*', '^murata,.*', '^mxic,.*', '^mxicy,.*', '^myir,.*', '^national,.*', '^neardi,.*', '^nec,.*', '^neofidelity,.*', '^neonode,.*', '^netcube,.*', '^netgear,.*', '^netlogic,.*', '^netron-dy,.*', '^netronix,.*', '^netxeon,.*', '^neweast,.*', '^newhaven,.*', '^newvision,.*', '^nexbox,.*', '^nextthing,.*', '^ni,.*', '^nintendo,.*', '^nlt,.*', '^nokia,.*', '^nordic,.*', '^nothing,.*', '^novatek,.*', '^novtech,.*', '^numonyx,.*', '^nutsboard,.*', '^nuvoton,.*', '^nvd,.*', '^nvidia,.*', '^nxp,.*', '^oceanic,.*', '^ocs,.*', '^oct,.*', '^okaya,.*', '^oki,.*', '^olimex,.*', '^olpc,.*', '^oneplus,.*', '^onie,.*', '^onion,.*', '^onnn,.*', '^ontat,.*', '^opalkelly,.*', '^openailab,.*', '^opencores,.*', '^openembed,.*', '^openpandora,.*', '^openrisc,.*', '^openwrt,.*', '^option,.*', '^oranth,.*', '^orisetech,.*', '^ortustech,.*', '^osddisplays,.*', '^osmc,.*', '^ouya,.*', '^overkiz,.*', '^ovti,.*', '^oxsemi,.*', '^ozzmaker,.*', '^panasonic,.*', '^parade,.*', '^parallax,.*', '^pda,.*', '^pegatron,.*', '^pericom,.*', '^pervasive,.*', '^phicomm,.*', '^phytec,.*', '^picochip,.*', '^pinctrl-[0-9]+$', '^pine64,.*', '^pineriver,.*', '^pixcir,.*', '^plantower,.*', '^plathome,.*', '^plda,.*', '^plx,.*', '^ply,.*', '^pni,.*', '^pocketbook,.*', '^polaroid,.*', '^polyhex,.*', '^portwell,.*', '^poslab,.*', '^pov,.*', '^powertip,.*', '^powervr,.*', '^powkiddy,.*', '^pri,.*', '^primeview,.*', '^primux,.*', '^probox2,.*', '^prt,.*', '^pulsedlight,.*', '^purism,.*', '^puya,.*', '^qca,.*', '^qcom,.*', '^qemu,.*', '^qi,.*', '^qiaodian,.*', '^qihua,.*', '^qishenglong,.*', '^qnap,.*', '^quanta,.*', '^radxa,.*', '^raidsonic,.*', '^ralink,.*', '^ramtron,.*', '^raspberrypi,.*', '^raydium,.*', '^rda,.*', '^realtek,.*', '^relfor,.*', '^remarkable,.*', '^renesas,.*', '^rervision,.*', '^retronix,.*', '^revotics,.*', '^rex,.*', '^richtek,.*', '^ricoh,.*', '^rikomagic,.*', '^riot,.*', '^riscv,.*', '^rockchip,.*', '^rocktech,.*', '^rohm,.*', '^ronbo,.*', '^roofull,.*', '^roseapplepi,.*', '^rve,.*', '^saef,.*', '^sakurapi,.*', '^samsung,.*', '^samtec,.*', '^sancloud,.*', '^sandisk,.*', '^satoz,.*', '^sbs,.*', '^schindler,.*', '^schneider,.*', '^sciosense,.*', '^seagate,.*', '^seeed,.*', '^seirobotics,.*', '^semtech,.*', '^senseair,.*', '^sensirion,.*', '^sensortek,.*', '^sercomm,.*', '^sff,.*', '^sgd,.*', '^sgmicro,.*', '^sgx,.*', '^sharp,.*', '^shift,.*', '^shimafuji,.*', '^shineworld,.*', '^shiratech,.*', '^si-en,.*', '^si-linux,.*', '^siemens,.*', '^sifive,.*', '^siflower,.*', '^sigma,.*', '^sii,.*', '^sil,.*', '^silabs,.*', '^silan,.*', '^silead,.*', '^silergy,.*', '^silex-insight,.*', '^siliconfile,.*', '^siliconmitus,.*', '^silvaco,.*', '^simtek,.*', '^sinlinx,.*', '^sinovoip,.*', '^sinowealth,.*', '^sipeed,.*', '^sirf,.*', '^sis,.*', '^sitronix,.*', '^skov,.*', '^skyworks,.*', '^smartfiber,.*', '^smartlabs,.*', '^smartrg,.*', '^smi,.*', '^smsc,.*', '^snps,.*', '^sochip,.*', '^socionext,.*', '^solidrun,.*', '^solomon,.*', '^sony,.*', '^sophgo,.*', '^sourceparts,.*', '^spacemit,.*', '^spansion,.*', '^sparkfun,.*', '^spinalhdl,.*', '^sprd,.*', '^square,.*', '^ssi,.*', '^sst,.*', '^sstar,.*', '^st,.*', '^st-ericsson,.*', '^starfive,.*', '^starry,.*', '^startek,.*', '^starterkit,.*', '^ste,.*', '^stericsson,.*', '^storlink,.*', '^storm,.*', '^storopack,.*', '^summit,.*', '^sunchip,.*', '^sundance,.*', '^sunplus,.*', '^supermicro,.*', '^swir,.*', '^syna,.*', '^synology,.*', '^synopsys,.*', '^tbs,.*', '^tbs-biometrics,.*', '^tcg,.*', '^tcl,.*', '^tcs,.*', '^tcu,.*', '^tdo,.*', '^team-source-display,.*', '^technexion,.*', '^technologic,.*', '^techstar,.*', '^techwell,.*', '^teejet,.*', '^teltonika,.*', '^tempo,.*', '^terasic,.*', '^tesla,.*', '^test,.*', '^tfc,.*', '^thead,.*', '^thine,.*', '^thingyjp,.*', '^thundercomm,.*', '^thwc,.*', '^ti,.*', '^tianma,.*', '^tlm,.*', '^tmt,.*', '^topeet,.*', '^topic,.*', '^topland,.*', '^toppoly,.*', '^topwise,.*', '^toradex,.*', '^toshiba,.*', '^toumaz,.*', '^tpk,.*', '^tplink,.*', '^tpo,.*', '^tq,.*', '^transpeed,.*', '^traverse,.*', '^tronfy,.*', '^tronsmart,.*', '^truly,.*', '^tsd,.*', '^turing,.*', '^tyan,.*', '^tyhx,.*', '^u-blox,.*', '^u-boot,.*', '^ubnt,.*', '^ucrobotics,.*', '^udoo,.*', '^ufispace,.*', '^ugoos,.*', '^ultratronik,.*', '^uni-t,.*', '^uniwest,.*', '^upisemi,.*', '^urt,.*', '^usi,.*', '^usr,.*', '^utoo,.*', '^v3,.*', '^vaisala,.*', '^vamrs,.*', '^variscite,.*', '^vdl,.*', '^vertexcom,.*', '^via,.*', '^vialab,.*', '^vicor,.*', '^videostrong,.*', '^virtio,.*', '^virtual,.*', '^vishay,.*', '^visionox,.*', '^vitesse,.*', '^vivante,.*', '^vivax,.*', '^vocore,.*', '^voipac,.*', '^voltafield,.*', '^vot,.*', '^vscom,.*', '^vxt,.*', '^wacom,.*', '^wanchanglong,.*', '^wand,.*', '^waveshare,.*', '^wd,.*', '^we,.*', '^welltech,.*', '^wetek,.*', '^wexler,.*', '^whwave,.*', '^wi2wi,.*', '^widora,.*', '^wiligear,.*', '^willsemi,.*', '^winbond,.*', '^wingtech,.*', '^winlink,.*', '^winsen,.*', '^winstar,.*', '^wirelesstag,.*', '^wits,.*', '^wlf,.*', '^wm,.*', '^wobo,.*', '^wolfvision,.*', '^x-powers,.*', '^xen,.*', '^xes,.*', '^xiaomi,.*', '^xillybus,.*', '^xingbangda,.*', '^xinpeng,.*', '^xiphera,.*', '^xlnx,.*', '^xnano,.*', '^xunlong,.*', '^xylon,.*', '^yadro,.*', '^yamaha,.*', '^yes-optoelectronics,.*', '^yic,.*', '^yiming,.*', '^ylm,.*', '^yna,.*', '^yones-toptech,.*', '^ys,.*', '^ysoft,.*', '^yuridenki,.*', '^yuzukihd,.*', '^zarlink,.*', '^zealz,.*', '^zeitec,.*', '^zidoo,.*', '^zii,.*', '^zinitix,.*', '^zkmagic,.*', '^zte,.*', '^zyxel,.*' from schema $id: http://devicetree.org/schemas/vendor-prefixes.yaml# doc reference errors (make refcheckdocs): See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20250703035639.7252-4-nick.li@foursemi.com The base for the series is generally the latest rc1. A different dependency should be noted in *this* patch. If you already ran 'make dt_binding_check' and didn't see the above error(s), then make sure 'yamllint' is installed and dt-schema is up to date: pip3 install dtschema --upgrade Please check and re-submit after running the above command yourself. Note that DT_SCHEMA_FILES can be set to your schema file to speed up checking your schema. However, it must be unset to test all examples with your schema.
© 2016 - 2025 Red Hat, Inc.