From: inki.dae@samsung.com (Inki Dae)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dt-bindings: exynos: Document #sound-dai-cells property of the HDMI node
Date: Fri, 09 Mar 2018 11:35:55 +0900 [thread overview]
Message-ID: <5AA1F30B.8010607@samsung.com> (raw)
In-Reply-To: <e3e1c628-d88f-6fb4-171e-a49c7ee38135@samsung.com>
Hi Sylwester,
2018? 03? 08? 20:22? Sylwester Nawrocki ?(?) ? ?:
> Hi Inki,
>
> Cc: alsa-devel at alsa-project.org
>
> On 03/08/2018 09:15 AM, Inki Dae wrote:
>> By the way, it seems 'sound-dai-cells' property never affect Exynos4210/4212> 5420/5433. It seems that even through ALSA TM2 audio driver(tm2_wm5110.c)
>> exists the driver never check the property.
>>
>> However, this patch adds below description.
>>
>> "Optional properties for Exynos 4210, 4212, 5420 and 5433"
>>
>> Is there a possibility for other boards based on Exynos4210/4212/5420/5433
>> SoC to use this property later?
>
> All these SoCs have the HDMI IP block which has one input DAI, connected
> internally over I2S bus with the IS2 controller.
>
> I think there is no advantage in limiting ourselves now only to SoC's
> for which we currently rely on that DT property in current kernel code,
> just to update this documentation later when we actually put the property
> in dts files.
>
> In case of exynos5420 we already require #sound-dai-cells for Odroid and
Maybe exynos5422? Odroid XU3/4 use Exynos5422.
> I have also a patch for exynos5420-peach-pit board which will need it as
> well.
>
> As far as exynos4210 and exynos4212 are concerned it's a matter of adding
> support for Odroid-U3, then we will also need this property because
> we are going to use "multi-codec" (HDMI and external I2S0 pins for CODEC
> are wired in parallel).
>
> In case of exynos5433 it just happens that the code in current driver
> doesn't require #sound-dai-cells property - one of the reasons I made it
> this way was to avoid dependency on dts, but it doesn't imply we should
> describe the HW in DT incompletely. Once the property is in dtbs we can
> update the driver to use more generic code, instead of open coding things.
>
Good idea.
> Actually I have forgotten to add also exynos5250 to the list.
Seems that '#sound-dai-cells' is required mandatorily in case of Exynos5422 because Odroid XU3/4 Audio driver checks this property, and the driver returns error if the property doesn't exist in its device tree.
And if other SoCs - Exynos4210/4212/5250/5420/5433 - require this property with additional driver works later then this property would also be required mandatorily for them not optionally. In this case we may need to modify the description again.
So my opinion is to add only the description required mandatorily if I understood correctly.
Thanks,
Inki Dae
>
next prev parent reply other threads:[~2018-03-09 2:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180307171131epcas1p4687ef394d1a0a6d0eb2de2691c977c3f@epcas1p4.samsung.com>
2018-03-07 17:11 ` [PATCH] dt-bindings: exynos: Document #sound-dai-cells property of the HDMI node Sylwester Nawrocki
2018-03-08 2:41 ` Rob Herring
2018-03-08 4:01 ` Inki Dae
2018-03-08 6:29 ` Marek Szyprowski
2018-03-08 6:50 ` Inki Dae
2018-03-08 7:36 ` Marek Szyprowski
2018-03-08 8:15 ` Inki Dae
2018-03-08 11:22 ` Sylwester Nawrocki
2018-03-09 2:35 ` Inki Dae [this message]
2018-03-09 11:10 ` Sylwester Nawrocki
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=5AA1F30B.8010607@samsung.com \
--to=inki.dae@samsung.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox