All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Bee <knaerzche@gmail.com>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	Alex Bee <knaerzche@gmail.com>
Subject: [PATCH 0/2] Add RK3128's sound nodes
Date: Mon,  6 May 2024 17:51:01 +0200	[thread overview]
Message-ID: <20240506155103.206592-1-knaerzche@gmail.com> (raw)

RK3128 has two I2S, and one S/PDIF controller. They are already supported
by the drivers and covered by the bindings. All it needs to make use of
them is exposing them in the SoC device tree.

Alex Bee (2):
  ARM: dts: rockchip: Add i2s nodes for RK3128
  ARM: dts: rockchip: Add spdif node for RK3128

 arch/arm/boot/dts/rockchip/rk3128.dtsi | 41 ++++++++++++++++++++++++++
 1 file changed, 41 insertions(+)

-- 
2.43.2


_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

WARNING: multiple messages have this Message-ID (diff)
From: Alex Bee <knaerzche@gmail.com>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	Alex Bee <knaerzche@gmail.com>
Subject: [PATCH 0/2] Add RK3128's sound nodes
Date: Mon,  6 May 2024 17:51:01 +0200	[thread overview]
Message-ID: <20240506155103.206592-1-knaerzche@gmail.com> (raw)

RK3128 has two I2S, and one S/PDIF controller. They are already supported
by the drivers and covered by the bindings. All it needs to make use of
them is exposing them in the SoC device tree.

Alex Bee (2):
  ARM: dts: rockchip: Add i2s nodes for RK3128
  ARM: dts: rockchip: Add spdif node for RK3128

 arch/arm/boot/dts/rockchip/rk3128.dtsi | 41 ++++++++++++++++++++++++++
 1 file changed, 41 insertions(+)

-- 
2.43.2


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Alex Bee <knaerzche@gmail.com>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	Alex Bee <knaerzche@gmail.com>
Subject: [PATCH 0/2] Add RK3128's sound nodes
Date: Mon,  6 May 2024 17:51:01 +0200	[thread overview]
Message-ID: <20240506155103.206592-1-knaerzche@gmail.com> (raw)

RK3128 has two I2S, and one S/PDIF controller. They are already supported
by the drivers and covered by the bindings. All it needs to make use of
them is exposing them in the SoC device tree.

Alex Bee (2):
  ARM: dts: rockchip: Add i2s nodes for RK3128
  ARM: dts: rockchip: Add spdif node for RK3128

 arch/arm/boot/dts/rockchip/rk3128.dtsi | 41 ++++++++++++++++++++++++++
 1 file changed, 41 insertions(+)

-- 
2.43.2


             reply	other threads:[~2024-05-06 15:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 15:51 Alex Bee [this message]
2024-05-06 15:51 ` [PATCH 0/2] Add RK3128's sound nodes Alex Bee
2024-05-06 15:51 ` Alex Bee
2024-05-06 15:51 ` [PATCH 1/2] ARM: dts: rockchip: Add i2s nodes for RK3128 Alex Bee
2024-05-06 15:51   ` Alex Bee
2024-05-06 15:51   ` Alex Bee
2024-05-06 15:51 ` [PATCH 2/2] ARM: dts: rockchip: Add spdif node " Alex Bee
2024-05-06 15:51   ` Alex Bee
2024-05-06 15:51   ` Alex Bee
2024-06-08 15:17 ` [PATCH 0/2] Add RK3128's sound nodes Heiko Stuebner
2024-06-08 15:17   ` Heiko Stuebner
2024-06-08 15:17   ` Heiko Stuebner

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=20240506155103.206592-1-knaerzche@gmail.com \
    --to=knaerzche@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.