From: Mark Brown <broonie@kernel.org>
To: Tzung-Bi Shih <tzungbi@google.com>
Cc: Hariprasad Kelam <hariprasad.kelam@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
howie.huang@mediatek.com, Takashi Iwai <tiwai@suse.com>,
ALSA development <alsa-devel@alsa-project.org>,
Jiaxin Yu <jiaxin.yu@mediatek.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-mediatek@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ASoC: mediatek: mt6358: support DMIC one-wire mode
Date: Fri, 29 May 2020 14:05:40 +0100 [thread overview]
Message-ID: <20200529130539.GK4610@sirena.org.uk> (raw)
In-Reply-To: <CA+Px+wVSwJK-=75chKLjSEe3bPRtV2wD95W5D_pdR0Pw0G470A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
On Fri, May 29, 2020 at 07:22:43PM +0800, Tzung-Bi Shih wrote:
> On Fri, May 29, 2020 at 7:09 PM Mark Brown <broonie@kernel.org> wrote:
> > What is DMIC one wire mode? This doesn't sound like something I'd
> > expect to vary at runtime.
> It means: 1 PDM data wire carries 2 channel data (rising edge for left
> and falling edge for right).
I thought that was normal for DMICs - is this selecting between left and
right or something?
> The setting shouldn't and won't change at runtime. Would you suggest
> putting it into DTS binding?
Yes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Tzung-Bi Shih <tzungbi@google.com>
Cc: Hariprasad Kelam <hariprasad.kelam@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
howie.huang@mediatek.com, Takashi Iwai <tiwai@suse.com>,
ALSA development <alsa-devel@alsa-project.org>,
Jiaxin Yu <jiaxin.yu@mediatek.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-mediatek@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ASoC: mediatek: mt6358: support DMIC one-wire mode
Date: Fri, 29 May 2020 14:05:40 +0100 [thread overview]
Message-ID: <20200529130539.GK4610@sirena.org.uk> (raw)
In-Reply-To: <CA+Px+wVSwJK-=75chKLjSEe3bPRtV2wD95W5D_pdR0Pw0G470A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 548 bytes --]
On Fri, May 29, 2020 at 07:22:43PM +0800, Tzung-Bi Shih wrote:
> On Fri, May 29, 2020 at 7:09 PM Mark Brown <broonie@kernel.org> wrote:
> > What is DMIC one wire mode? This doesn't sound like something I'd
> > expect to vary at runtime.
> It means: 1 PDM data wire carries 2 channel data (rising edge for left
> and falling edge for right).
I thought that was normal for DMICs - is this selecting between left and
right or something?
> The setting shouldn't and won't change at runtime. Would you suggest
> putting it into DTS binding?
Yes.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Tzung-Bi Shih <tzungbi@google.com>
Cc: Hariprasad Kelam <hariprasad.kelam@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
howie.huang@mediatek.com, Takashi Iwai <tiwai@suse.com>,
ALSA development <alsa-devel@alsa-project.org>,
Jiaxin Yu <jiaxin.yu@mediatek.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-mediatek@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ASoC: mediatek: mt6358: support DMIC one-wire mode
Date: Fri, 29 May 2020 14:05:40 +0100 [thread overview]
Message-ID: <20200529130539.GK4610@sirena.org.uk> (raw)
In-Reply-To: <CA+Px+wVSwJK-=75chKLjSEe3bPRtV2wD95W5D_pdR0Pw0G470A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 548 bytes --]
On Fri, May 29, 2020 at 07:22:43PM +0800, Tzung-Bi Shih wrote:
> On Fri, May 29, 2020 at 7:09 PM Mark Brown <broonie@kernel.org> wrote:
> > What is DMIC one wire mode? This doesn't sound like something I'd
> > expect to vary at runtime.
> It means: 1 PDM data wire carries 2 channel data (rising edge for left
> and falling edge for right).
I thought that was normal for DMICs - is this selecting between left and
right or something?
> The setting shouldn't and won't change at runtime. Would you suggest
> putting it into DTS binding?
Yes.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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: Mark Brown <broonie@kernel.org>
To: Tzung-Bi Shih <tzungbi@google.com>
Cc: Jiaxin Yu <jiaxin.yu@mediatek.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Takashi Iwai <tiwai@suse.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Hariprasad Kelam <hariprasad.kelam@gmail.com>,
ALSA development <alsa-devel@alsa-project.org>,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
howie.huang@mediatek.com
Subject: Re: [PATCH] ASoC: mediatek: mt6358: support DMIC one-wire mode
Date: Fri, 29 May 2020 14:05:40 +0100 [thread overview]
Message-ID: <20200529130539.GK4610@sirena.org.uk> (raw)
In-Reply-To: <CA+Px+wVSwJK-=75chKLjSEe3bPRtV2wD95W5D_pdR0Pw0G470A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
On Fri, May 29, 2020 at 07:22:43PM +0800, Tzung-Bi Shih wrote:
> On Fri, May 29, 2020 at 7:09 PM Mark Brown <broonie@kernel.org> wrote:
> > What is DMIC one wire mode? This doesn't sound like something I'd
> > expect to vary at runtime.
> It means: 1 PDM data wire carries 2 channel data (rising edge for left
> and falling edge for right).
I thought that was normal for DMICs - is this selecting between left and
right or something?
> The setting shouldn't and won't change at runtime. Would you suggest
> putting it into DTS binding?
Yes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-05-29 13:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 11:04 [PATCH] ASoC: mediatek: mt6358: support DMIC one-wire mode Jiaxin Yu
2020-05-29 11:04 ` Jiaxin Yu
2020-05-29 11:04 ` Jiaxin Yu
2020-05-29 11:04 ` Jiaxin Yu
2020-05-29 11:09 ` Mark Brown
2020-05-29 11:09 ` Mark Brown
2020-05-29 11:09 ` Mark Brown
2020-05-29 11:09 ` Mark Brown
2020-05-29 11:22 ` Tzung-Bi Shih
2020-05-29 11:22 ` Tzung-Bi Shih
2020-05-29 11:22 ` Tzung-Bi Shih
2020-05-29 11:22 ` Tzung-Bi Shih
2020-05-29 13:05 ` Mark Brown [this message]
2020-05-29 13:05 ` Mark Brown
2020-05-29 13:05 ` Mark Brown
2020-05-29 13:05 ` Mark Brown
2020-05-29 17:26 ` Tzung-Bi Shih
2020-05-29 17:26 ` Tzung-Bi Shih
2020-05-29 17:26 ` Tzung-Bi Shih
2020-05-29 17:26 ` Tzung-Bi Shih
2020-05-29 18:16 ` Mark Brown
2020-05-29 18:16 ` Mark Brown
2020-05-29 18:16 ` Mark Brown
2020-05-29 18:16 ` 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=20200529130539.GK4610@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=hariprasad.kelam@gmail.com \
--cc=howie.huang@mediatek.com \
--cc=jiaxin.yu@mediatek.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=tiwai@suse.com \
--cc=tzungbi@google.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.