From: Heiko Stuebner <heiko@sntech.de>
To: Johan Jonker <jbx6244@gmail.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
linux-rockchip@lists.infradead.org, sugar.zhang@rock-chips.com,
robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, lgirdwood@gmail.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
broonie@kernel.org
Subject: Re: [PATCH v2 1/2] ASoC: rockchip-spdif: add description for rk3308
Date: Sun, 30 Aug 2020 21:42:29 +0200 [thread overview]
Message-ID: <159881654154.22245.11587351037887788062.b4-ty@sntech.de> (raw)
In-Reply-To: <20200818143727.5882-1-jbx6244@gmail.com>
On Tue, 18 Aug 2020 16:37:26 +0200, Johan Jonker wrote:
> A test with the command below shows that the compatible string
>
> "rockchip,rk3308-spdif", "rockchip,rk3328-spdif"
>
> is already in use, but is not added to a document.
> The current fallback string "rockchip,rk3328-spdif" points to a data
> set enum RK_SPDIF_RK3366 in rockchip_spdif.c that is not used both
> in the mainline as in the manufacturer kernel.
> (Of the enum only RK_SPDIF_RK3288 is used.)
> So if the properties don't change we might as well use the first SoC
> in line as fallback string and add the description for rk3308 as:
>
> [...]
Applied, thanks!
[1/1] arm64: dts: rockchip: change spdif fallback compatible on rk3308
commit: bc1f9bff0629a15e3de1ef106ac03cba930227dd
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
prev parent reply other threads:[~2020-08-30 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 14:37 [PATCH v2 1/2] ASoC: rockchip-spdif: add description for rk3308 Johan Jonker
2020-08-18 14:37 ` [PATCH v2 2/2] arm64: dts: rockchip: change fallback string rockchip,rk3308-spdif Johan Jonker
2020-08-18 17:39 ` [PATCH v2 1/2] ASoC: rockchip-spdif: add description for rk3308 Mark Brown
2020-08-30 19:42 ` Heiko Stuebner [this message]
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=159881654154.22245.11587351037887788062.b4-ty@sntech.de \
--to=heiko@sntech.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbx6244@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=sugar.zhang@rock-chips.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).