[PATCH 2/2] ASoC: dt-bindings: rt1015p: add new compatible id
Add new compatible ID for rt1015p in dt-bindings document.
Signed-off-by: Jack Yu jack.yu@realtek.com --- Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml b/Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml index 644b68edf3e1..8fcb5f79a1b5 100644 --- a/Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml +++ b/Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml @@ -15,7 +15,9 @@ description: |
properties: compatible: - const: realtek,rt1015p + oneOf: + const: realtek,rt1015p + const: realtek,rt1019p
sdb-gpios: description:
On Mon, Aug 9, 2021 at 4:27 AM Jack Yu jack.yu@realtek.com wrote:
Add new compatible ID for rt1015p in dt-bindings document.
Please resend without the winmail.dat attachment. And run 'make dt_binding_check' as this will fail.
Signed-off-by: Jack Yu jack.yu@realtek.com
Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml b/Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml index 644b68edf3e1..8fcb5f79a1b5 100644 --- a/Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml +++ b/Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml @@ -15,7 +15,9 @@ description: |
properties: compatible:
- const: realtek,rt1015p
oneOf:const: realtek,rt1015pconst: realtek,rt1019psdb-gpios: description:
-- 2.31.1
On Mon, 9 Aug 2021 10:27:14 +0000, Jack Yu wrote:
Add new compatible ID for rt1015p in dt-bindings document.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[2/2] ASoC: dt-bindings: rt1015p: add new compatible id commit: 064478e4877c76b0c1fd1155934f226f1561aab3
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)
-
Jack Yu -
Mark Brown -
Rob Herring