[PATCH v3 1/2] ASoC: dt-bindings: irondevice,sma1307: Add initial DT binding
This adds the schema binding for the Iron Device SMA1307 Amp
Signed-off-by: Kiseok Jo kiseok.jo@irondevice.com --- .../bindings/sound/irondevice,sma1307.yaml | 54 ++++++++++++++++++++++ 1 file changed, 54 insertions(+)
diff --git a/Documentation/devicetree/bindings/sound/irondevice,sma1307.yaml b/Documentation/devicetree/bindings/sound/irondevice,sma1307.yaml new file mode 100644 index 000000000..0bb4ee664 --- /dev/null +++ b/Documentation/devicetree/bindings/sound/irondevice,sma1307.yaml @@ -0,0 +1,54 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) %YAML 1.2 +--- +$id: http://devicetree.org/schemas/sound/irondevice,sma1307.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Iron Device SMA1307 Audio Amplifier + +maintainers: + - Kiseok Jo kiseok.jo@irondevice.com + +description: + SMA1307 boosted digital speaker amplifier + with feedback-loop. + +allOf: + - $ref: dai-common.yaml# + +properties: + compatible: + enum: + - irondevice,sma1307a + - irondevice,sma1307aq + description: + If a 'q' is added, it indicated the product is AEC-Q100 + qualified for automotive applications. SMA1307A supports + both WLCSP and QFN packages. However, SMA1307AQ only + supports the QFN package. + + reg: + maxItems: 1 + + '#sound-dai-cells': + const: 1 + +required: + - compatible + - reg + - '#sound-dai-cells' + +additionalProperties: false + +examples: + - | + i2c { + #address-cells = <1>; + #size-cells = <0>; + + amplifier@1e { + compatible = "irondevice,sma1307a"; + reg = <0x1e>; + #sound-dai-cells = <1>; + }; + };
-- 2.39.2
On Mon, Nov 04, 2024 at 07:33:47AM +0000, Ki-Seok Jo wrote:
I don't see the rest of the series (I fetch from lore). That means your threading is broken.
This adds the schema binding for the Iron Device SMA1307 Amp
Signed-off-by: Kiseok Jo kiseok.jo@irondevice.com
v3, but where is the revision history?
.../bindings/sound/irondevice,sma1307.yaml | 54 ++++++++++++++++++++++ 1 file changed, 54 insertions(+)
diff --git a/Documentation/devicetree/bindings/sound/irondevice,sma1307.yaml b/Documentation/devicetree/bindings/sound/irondevice,sma1307.yaml new file mode 100644 index 000000000..0bb4ee664 --- /dev/null +++ b/Documentation/devicetree/bindings/sound/irondevice,sma1307.yaml @@ -0,0 +1,54 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) %YAML 1.2
"%YAML 1.2" goes on the 2nd line.
+--- +$id: http://devicetree.org/schemas/sound/irondevice,sma1307.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml#
+title: Iron Device SMA1307 Audio Amplifier
+maintainers:
- Kiseok Jo kiseok.jo@irondevice.com
+description:
- SMA1307 boosted digital speaker amplifier
- with feedback-loop.
Wrap lines at 80 char.
+allOf:
- $ref: dai-common.yaml#
+properties:
- compatible:
- enum:
- irondevice,sma1307a
- irondevice,sma1307aq
- description:
If a 'q' is added, it indicated the product is AEC-Q100
qualified for automotive applications. SMA1307A supports
both WLCSP and QFN packages. However, SMA1307AQ only
supports the QFN package.
Is this difference visible to software? The package is not, so that part is irrelevant.
- reg:
- maxItems: 1
- '#sound-dai-cells':
- const: 1
+required:
- compatible
- reg
- '#sound-dai-cells'
+additionalProperties: false
+examples:
- |
- i2c {
#address-cells = <1>;
#size-cells = <0>;
amplifier@1e {
compatible = "irondevice,sma1307a";
reg = <0x1e>;
#sound-dai-cells = <1>;
};
- };
-- 2.39.2
On Mon, Nov 04, 2024 at 10:17:51AM -0600, Rob Herring wrote:
On Mon, Nov 04, 2024 at 07:33:47AM +0000, Ki-Seok Jo wrote:
- enum:
- irondevice,sma1307a
- irondevice,sma1307aq
- description:
If a 'q' is added, it indicated the product is AEC-Q100
qualified for automotive applications. SMA1307A supports
both WLCSP and QFN packages. However, SMA1307AQ only
supports the QFN package.
Is this difference visible to software? The package is not, so that part is irrelevant.
It seems reasonable to allow it as a compatible if it's sold as a separate part, even if we don't need to care.
On Mon, Nov 04, 2024 at 07:33:47AM +0000, Ki-Seok Jo wrote:
I don't see the rest of the series (I fetch from lore). That means your threading is broken.
Okay, I see.
It appears that using the b4 tool this time may have caused some issues, resulting in the removal of previous content. I would appreciate any suggestions you might have for reconnecting the series. Thank you!
This adds the schema binding for the Iron Device SMA1307 Amp
Signed-off-by: Kiseok Jo kiseok.jo@irondevice.com
v3, but where is the revision history?
Yes, that sounds good. Thank you!
There are changes before v2, but there are no changes in this section when transitioning to v3, so I didn't include anything.
Would it be better to add the previous changes and indicate that there are no changes when moving to v3?
Thank you for your help! I'll reflect on the points you've mentioned and update it to v4.
If I download the source again, make the necessary modifications, and then just change the version to v4 before sending it, could that cause the threading to break again?
On Mon, 04 Nov 2024 07:33:47 +0000, Ki-Seok Jo wrote:
This adds the schema binding for the Iron Device SMA1307 Amp
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] ASoC: dt-bindings: irondevice,sma1307: Add initial DT binding (no commit info) [2/2] ASoC: sma1307: Add driver for Iron Device SMA1307 commit: 576c57e6b4c1d734bcb7cc33dde9a99a9383b520
All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying to this mail.
Thanks, Mark
participants (3)
-
Ki-Seok Jo
-
Mark Brown
-
Rob Herring