From: Mark Brown <broonie@kernel.org>
To: David Heidelberg <david@ixit.cz>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Oder Chiou <oder_chiou@realtek.com>,
~okias/devicetree@lists.sr.ht, alsa-devel@alsa-project.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: dt-bindings: add missing pins
Date: Mon, 13 Dec 2021 16:34:52 +0000 [thread overview]
Message-ID: <Ybd2LMZ8+UqcUZTS@sirena.org.uk> (raw)
In-Reply-To: <20211211215120.70966-1-david@ixit.cz>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
On Sat, Dec 11, 2021 at 10:51:19PM +0100, David Heidelberg wrote:
> Add pins missing in documentation, but present in the hardware.
> Fixes: 0e826e867264 ("ASoC: add RT5677 CODEC driver")
Please don't just add nonsense fixes tags for the sake of it, this just
creates noise and gets in the way of people trying to use the tags to
work out if thy need fixes. The commit you're mentioning doesn't even
contain any changes to the binding document.
> @@ -54,9 +54,21 @@ Pins on the device (for linking into audio routes):
> * DMIC2
> * DMIC3
> * DMIC4
> + * DMIC L1
> + * DMIC L2
> + * DMIC L3
> + * DMIC L4
> + * DMIC R1
> + * DMIC R2
> + * DMIC R3
> + * DMIC R4
These clearly aren't pins you're adding, digital microphones use PDM
and carry a stereo pair on a single physical pin (which is what should
be and already is in the bindings). This is adding an extra set of pins
to the binding duplicating the existing ones.
> * LOUT1
> * LOUT2
> * LOUT3
> + * PDM1L
> + * PDM1R
> + * PDM2L
> + * PDM2R
I'd expect these to be just PDM1 and PDM2, assuming that that's what the
pins are called in the chip datasheet.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-12-13 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 21:51 [PATCH] ASoC: dt-bindings: add missing pins David Heidelberg
2021-12-13 16:34 ` Mark Brown [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=Ybd2LMZ8+UqcUZTS@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=robh+dt@kernel.org \
--cc=~okias/devicetree@lists.sr.ht \
/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).