From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms@verge.net.au>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
linux-renesas-soc@vger.kernel.org, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
devicetree@vger.kernel.org, magnus.damm@gmail.com,
linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 5/5] ARM: dts: r8a7794: add sound support
Date: Thu, 18 Feb 2016 22:31:31 +0300 [thread overview]
Message-ID: <56C61C13.8000301@cogentembedded.com> (raw)
In-Reply-To: <20160217234857.GA6886@verge.net.au>
On 02/18/2016 02:48 AM, Simon Horman wrote:
>>>>>>>>>>> Define the generic R8A7794 part of the sound device node.
>>>>>>>>>>> This sound device is a complex one and comprises the Audio Clock Generator
>>>>>>>>>>> (ADG), Sampling Rate Converter Unit (SCU), Serial Sound Interface [Unit]
>>>>>>>>>>> (SSI[U]), and Audio DMAC-Peripheral-Peripheral.
>>>>>>>>>>> It is up to the board file to enable the device.
>>>>>>>>>>>
>>>>>>>>>>> This patch is based on the R8A7791 sound work by Kuninori Morimoto.
>>>>>>>>>>>
>>>>>>>>>>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>>>>>>>>>> (snip)
>>>>>>>>>>> + rcar_sound,src {
>>>>>>>>>>> + src1: src@1 {
>>>>>>>>>>> + interrupts = <GIC_SPI 353 IRQ_TYPE_LEVEL_HIGH>;
>>>>>>>>>>> + dmas = <&audma0 0x87>, <&audma0 0x9c>;
>>>>>>>>>>> + dma-names = "rx", "tx";
>>>>>>>>>>> + };
>>>>>>>>>>> + src2: src@2 {
>>>>>>>>>>> + interrupts = <GIC_SPI 354 IRQ_TYPE_LEVEL_HIGH>;
>>>>>>>>>>> + dmas = <&audma0 0x89>, <&audma0 0x9e>;
>>>>>>>>>>> + dma-names = "rx", "tx";
>>>>>>>>>>> + };
>>>>>>>>>>> + src3: src@3 {
>>>>>>>>>>> + interrupts = <GIC_SPI 355 IRQ_TYPE_LEVEL_HIGH>;
>>>>>>>>>>> + dmas = <&audma0 0x8b>, <&audma0 0xa0>;
>>>>>>>>>>> + dma-names = "rx", "tx";
>>>>>>>>>>> + };
>>>>>>>>>>> + src4: src@4 {
>>>>>>>>>>> + interrupts = <GIC_SPI 356 IRQ_TYPE_LEVEL_HIGH>;
>>>>>>>>>>> + dmas = <&audma0 0x8d>, <&audma0 0xb0>;
>>>>>>>>>>> + dma-names = "rx", "tx";
>>>>>>>>>>> + };
>>>>>>>>>>> + src5: src@5 {
>>>>>>>>>>> + interrupts = <GIC_SPI 357 IRQ_TYPE_LEVEL_HIGH>;
>>>>>>>>>>> + dmas = <&audma0 0x8f>, <&audma0 0xb2>;
>>>>>>>>>>> + dma-names = "rx", "tx";
>>>>>>>>>>> + };
>>>>>>>>>>> + src6: src@6 {
>>>>>>>>>>> + interrupts = <GIC_SPI 358 IRQ_TYPE_LEVEL_HIGH>;
>>>>>>>>>>> + dmas = <&audma0 0x91>, <&audma0 0xb4>;
>>>>>>>>>>> + dma-names = "rx", "tx";
>>>>>>>>>>> + };
>>>>>>>>>>> + };
>>>>>>>>>>
>>>>>>>>>> I think this can't work correctly, because driver is assuming
>>>>>>>>>> DT has all channles (from 0). (see linux/sound/soc/sh/rcar/src.c :: rsnd_src_probe)
>>>>>>>>>> Can you adds dummy src0 with some comments ? or fix src.c driver ?
>>>>>>>>>
>>>>>>>>> I would prefer the driver to be fixed (I had a similar patchset locally
>>>>>>>>> and I found it doesn't work).
>>>>>>>>
>>>>>>>> You mean you had R8A7794 sound patch set too?
>>>>>>>
>>>>>>> Yes, I was working on it recently.
>>>>>>> I suppose we should coordinate these things in future to avoid
>>>>>>> duplicated effort.
>>>>>>
>>>>>> Yes, seems a good idea now. :-)
>>>>>>
>>>>>>>>> The reason is that DT should describe
>>>>>>>>> the hardware rather than the current state of the software.
>>>>>>>>
>>>>>>>> Yes, of course. Just tell me do I have to fix the driver *before* this
>>>>>>>> patch set is accepted?
>>>>>>
>>>>>>> I did not entirely get to the bottom of the problem, but I think that at
>>>>>>> the very least something needs to be done about the for_each_rsnd_src()
>>>>>>> loop in rsnd_src_probe.
>>>>>>
>>>>>> It's not that it replies to my question. :-)
>>>>>> So you're looking at this issue yourself?
>>>>>
>>>>> I have not got very far, as you can see, but I was planning to look into it.
>>>>> I don't mind if you want to do so.
>>>>
>>>> After consultation with the management, I'm going to look into this issue
>>>> myself. :-)
>>>
>>> Excellent.
>>
>> But not immediately. I have some other things to look at before that (DU
>> and AVB), they'll going to take some (significant) time... :-(
>>
>>> FWIW, I can test anything you come up with for the r8a7794 an alt board
>>
>> I have remote access to Alt now, in fact using it currently for the AVB work.
>>
>>> or post patches for it once you have r8a7794/silk sorted out.
>>
>> I already have audio on these working. Or you're going to wait until I
>> fix the SRC issue?
>
> I'm happy to merge a subset of your r8a7794/silk patches,
> that don't touch the SRC issue if you think that is appropriate.
I think you can merge everything R8A7794 specific. The SILK patch doesn't
make use of SRCs yet but depends on the PFC patches, so makes sense to hold it
up...
> From there I could get similar functionality running on the Alt - I don't
> expect that to be a difficult task.
Sure -- if you have direct access to the board.
> And then when you come back to the SRC
> issue we can enhance support for r8a7794/silk,alt.
Yes.
MBR, Sergei
next prev parent reply other threads:[~2016-02-18 19:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 21:52 [PATCH v2 0/5] Add R8A7794 sound DT support Sergei Shtylyov
2016-02-09 21:53 ` [PATCH v2 1/5] ARM: dts: r8a7794: add audio clocks Sergei Shtylyov
2016-02-09 21:54 ` [PATCH v2 2/5] ARM: dts: r8a7794: add MSTP5 clocks Sergei Shtylyov
2016-02-09 21:55 ` [PATCH v2 3/5] ARM: dts: r8a7794: add MSTP10 clocks Sergei Shtylyov
2016-02-09 21:56 ` [PATCH v2 4/5] ARM: dts: r8a7794: add Audio-DMAC support Sergei Shtylyov
2016-02-09 21:58 ` [PATCH v2 5/5] ARM: dts: r8a7794: add sound support Sergei Shtylyov
2016-02-10 0:41 ` Kuninori Morimoto
2016-02-10 17:14 ` Simon Horman
2016-02-12 16:47 ` Sergei Shtylyov
2016-02-12 18:43 ` Simon Horman
2016-02-12 19:08 ` Sergei Shtylyov
2016-02-12 19:33 ` Simon Horman
2016-02-12 19:57 ` Sergei Shtylyov
2016-02-17 5:38 ` Simon Horman
2016-02-17 19:07 ` Sergei Shtylyov
2016-02-17 23:48 ` Simon Horman
2016-02-18 19:31 ` Sergei Shtylyov [this message]
2016-02-10 18:09 ` Sergei Shtylyov
2016-02-10 3:12 ` Kuninori Morimoto
2016-02-10 18:10 ` Sergei Shtylyov
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=56C61C13.8000301@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=horms@verge.net.au \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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 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).