All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xing Zheng <zhengxing@rock-chips.com>
To: Mark Brown <broonie@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
	linux-rockchip@lists.infradead.org, dianders@chromium.org,
	heiko@sntech.de, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH v3] ASoC: rockchip: Add machine driver for MAX98357A/RT5514/DA7219
Date: Tue, 07 Jun 2016 19:38:23 +0800	[thread overview]
Message-ID: <5756B22F.9000105@rock-chips.com> (raw)
In-Reply-To: <20160607104711.GR7510@sirena.org.uk>

Hi Mark,

On 2016年06月07日 18:47, Mark Brown wrote:
> On Tue, Jun 07, 2016 at 10:49:35AM +0800, Xing Zheng wrote:
>> On 2016年06月07日 07:50, Mark Brown wrote:
>>> It should probably be three compatibles, one per CODEC, if the driver
>>> needs to handle each separately.
>> Do you mean like this:
>> --------
>> sound {
>> compatible = "rockchip,rk3399-max98357a-rt5514-da7219";
>>
>> dailink-0 {
>> compatible = "rockchip,rk3399-max98357a";
>> rockchip,cpu =<&i2s0>;
>> rockchip,codec =<&max98357a>;
>> };
>>
>> dailink-1 {
>> compatible = "rockchip,rk3399-rt5514";
>> rockchip,cpu =<&i2s0>;
>> rockchip,codec =<&headsetcodec>;
>> };
>>
>> dailink-2 {
>> compatible = "rockchip,rk3399-da7219";
>> rockchip,cpu =<&i2s0>;
>> rockchip,codec =<&codec>;
>> };
>> };
>> --------
>> Above, the machine drvier will handle them. Please correct me if I
>> misunderstand.
> No, that'd be one card with all three CODECs on the same board which I'm
> guessing isn't the intention?
Yes, because on our board, the audio connection by hardware really is such:
                   |-- max98357a
i2s0 <==> |-- rt5514
                   | -- da7219

We do need to support max98357a / rt5514 / da7219 via i2s0 on the same 
board for RK3399.

I remember that it will be failed if we register card with i2s0 more 
times. Therefore, I chose this mothod that create 3 dai-links on one 
machine driver.

Thanks.

-- 
- Xing Zheng

WARNING: multiple messages have this Message-ID (diff)
From: zhengxing@rock-chips.com (Xing Zheng)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] ASoC: rockchip: Add machine driver for MAX98357A/RT5514/DA7219
Date: Tue, 07 Jun 2016 19:38:23 +0800	[thread overview]
Message-ID: <5756B22F.9000105@rock-chips.com> (raw)
In-Reply-To: <20160607104711.GR7510@sirena.org.uk>

Hi Mark,

On 2016?06?07? 18:47, Mark Brown wrote:
> On Tue, Jun 07, 2016 at 10:49:35AM +0800, Xing Zheng wrote:
>> On 2016?06?07? 07:50, Mark Brown wrote:
>>> It should probably be three compatibles, one per CODEC, if the driver
>>> needs to handle each separately.
>> Do you mean like this:
>> --------
>> sound {
>> compatible = "rockchip,rk3399-max98357a-rt5514-da7219";
>>
>> dailink-0 {
>> compatible = "rockchip,rk3399-max98357a";
>> rockchip,cpu =<&i2s0>;
>> rockchip,codec =<&max98357a>;
>> };
>>
>> dailink-1 {
>> compatible = "rockchip,rk3399-rt5514";
>> rockchip,cpu =<&i2s0>;
>> rockchip,codec =<&headsetcodec>;
>> };
>>
>> dailink-2 {
>> compatible = "rockchip,rk3399-da7219";
>> rockchip,cpu =<&i2s0>;
>> rockchip,codec =<&codec>;
>> };
>> };
>> --------
>> Above, the machine drvier will handle them. Please correct me if I
>> misunderstand.
> No, that'd be one card with all three CODECs on the same board which I'm
> guessing isn't the intention?
Yes, because on our board, the audio connection by hardware really is such:
                   |-- max98357a
i2s0 <==> |-- rt5514
                   | -- da7219

We do need to support max98357a / rt5514 / da7219 via i2s0 on the same 
board for RK3399.

I remember that it will be failed if we register card with i2s0 more 
times. Therefore, I chose this mothod that create 3 dai-links on one 
machine driver.

Thanks.

-- 
- Xing Zheng

  reply	other threads:[~2016-06-07 11:38 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-26 13:02 [PATCH v3] ASoC: rockchip: Add machine driver for MAX98357A/RT5514/DA7219 Xing Zheng
2016-05-26 13:02 ` Xing Zheng
2016-05-30  7:32 ` Xing Zheng
2016-05-30  7:32   ` Xing Zheng
2016-05-30  7:32   ` Xing Zheng
     [not found]   ` <574BEC9D.50007-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-05-30 16:03     ` Mark Brown
2016-05-30 16:03       ` Mark Brown
2016-05-30 16:03       ` Mark Brown
2016-06-01 14:45 ` Rob Herring
2016-06-01 14:45   ` Rob Herring
2016-06-03 14:16   ` Xing Zheng
2016-06-03 14:16     ` Xing Zheng
2016-06-03 14:16     ` Xing Zheng
2016-06-06 23:50     ` Mark Brown
2016-06-06 23:50       ` Mark Brown
     [not found]       ` <20160606235026.GP7510-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-06-07  2:49         ` Xing Zheng
2016-06-07  2:49           ` Xing Zheng
2016-06-07  2:49           ` Xing Zheng
     [not found]           ` <5756363F.40208-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-06-07 10:47             ` Mark Brown
2016-06-07 10:47               ` Mark Brown
2016-06-07 10:47               ` Mark Brown
2016-06-07 11:38               ` Xing Zheng [this message]
2016-06-07 11:38                 ` Xing Zheng
     [not found]                 ` <5756B22F.9000105-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-06-07 12:06                   ` Mark Brown
2016-06-07 12:06                     ` Mark Brown
2016-06-07 12:06                     ` Mark Brown
2016-06-07 12:47                     ` Xing Zheng
2016-06-07 12:47                       ` Xing Zheng
2016-06-07 12:47                       ` Xing Zheng
     [not found]                       ` <5756C245.7010001-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-06-07 13:32                         ` Mark Brown
2016-06-07 13:32                           ` Mark Brown
2016-06-07 13:32                           ` Mark Brown
2016-06-07 13:48                           ` Xing Zheng
2016-06-07 13:48                             ` Xing Zheng
2016-06-07 13:48                             ` Xing Zheng
     [not found]                             ` <5756D0BA.7060702-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-06-07 14:54                               ` Mark Brown
2016-06-07 14:54                                 ` Mark Brown
2016-06-07 14:54                                 ` Mark Brown

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=5756B22F.9000105@rock-chips.com \
    --to=zhengxing@rock-chips.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=galak@codeaurora.org \
    --cc=heiko@sntech.de \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=perex@perex.cz \
    --cc=robh@kernel.org \
    --cc=tiwai@suse.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 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.