From: Maxime Ripard <mripard@kernel.org>
To: Matteo Martelli <matteomartelli3@gmail.com>
Cc: "Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>, "Chen-Yu Tsai" <wens@csie.org>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Samuel Holland" <samuel@sholland.org>,
"Marcus Cooper" <codekipper@gmail.com>,
"Clément Péron" <peron.clem@gmail.com>,
linux-sound@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] ASoC: sunxi: sun4i-i2s: fix LRCLK polarity in i2s mode
Date: Mon, 15 Jul 2024 16:29:52 +0200 [thread overview]
Message-ID: <20240715-rigorous-bipedal-sloth-c8df1b@houat> (raw)
In-Reply-To: <668419fb8ef9f_2a76d370f1@njaxe.notmuch>
[-- Attachment #1: Type: text/plain, Size: 2318 bytes --]
On Tue, Jul 02, 2024 at 05:17:15PM GMT, Matteo Martelli wrote:
> Maxime Ripard wrote:
> > On Fri, Jun 07, 2024 at 10:04:43AM GMT, Matteo Martelli wrote:
> > > Maxime Ripard wrote:
> > > > > - /*
> > > > > - * DAI clock polarity
> > > > > - *
> > > > > - * The setup for LRCK contradicts the datasheet, but under a
> > > > > - * scope it's clear that the LRCK polarity is reversed
> > > > > - * compared to the expected polarity on the bus.
> > > > > - */
> > > >
> > > > I think we should keep that comment somewhere.
> > >
> > > I think that keeping that comment would be very misleading since the LRCLK
> > > setup would not contradict the datasheet anymore [1][2].
> > >
> > > Also, do you recall any details about the mentioned scope test setup? Was i2s
> > > mode tested in that occasion? It would help clarify the situation.
> >
> > I can't remember if I tested i2s, I think I did though. But most of the
> > work was done on either TDM or DSP modes, and I remember very clearly
> > that the LRCK polarity was inverted compared to what Allwinner documents.
> >
> > So the doc was, at best, misleading for these formats and we should keep
> > the comments.
>
> Thanks for the reply Maxime, would you be able to point out the Allwinner
> document part that is (or was) misleading? The current datasheets (see links
> [1][2]) look correct, the current driver setup for TDM and DSP modes respects
> those datasheets and it's not "reversed compared to the expected polarity on
> the bus" as the comment states.
I clearly remember having to debug something there, but I don't remember
much more, sorry.
I guess if you have tested on the H3 I2S, TDM and DSP and it all works
as expected with your changes, go ahead and ignore my comment then.
> Also I didn't find any related errata in their changelog.
Yeah... Allwinner doesn't do errata.
> Could it be possible that during those mentioned tests you
> were still referring to the datasheets of other SoCs like A10 for
> instance? Or maybe that the misleading information was in another
> document rather than the main datasheets? If that's the case, would
> you still think that the comment should be kept as it is?
Possibly, or an older version of the datasheet, I really can't remember.
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]
next prev parent reply other threads:[~2024-07-15 14:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 14:00 [PATCH 0/1] ASoC: sunxi: sun4i-i2s: fix LRCLK polarity in i2s mode Matteo Martelli
2024-05-29 14:00 ` Matteo Martelli
2024-05-29 14:00 ` [PATCH 1/1] " Matteo Martelli
2024-05-29 14:00 ` Matteo Martelli
2024-06-06 16:11 ` Maxime Ripard
2024-06-06 16:11 ` Maxime Ripard
2024-06-07 8:04 ` Matteo Martelli
2024-06-07 8:04 ` Matteo Martelli
2024-06-26 19:04 ` Mark Brown
2024-06-28 16:07 ` Matteo Martelli
2024-07-02 13:42 ` Maxime Ripard
2024-07-02 15:17 ` Matteo Martelli
2024-07-15 14:29 ` Maxime Ripard [this message]
2024-07-16 9:27 ` Matteo Martelli
2024-05-29 14:14 ` [PATCH 0/1] " Mark Brown
2024-05-29 14:14 ` Mark Brown
2024-05-29 14:19 ` Matteo Martelli
2024-05-29 14:19 ` Matteo Martelli
2024-05-29 14:23 ` Mark Brown
2024-05-29 14:23 ` 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=20240715-rigorous-bipedal-sloth-c8df1b@houat \
--to=mripard@kernel.org \
--cc=broonie@kernel.org \
--cc=codekipper@gmail.com \
--cc=jernej.skrabec@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=matteomartelli3@gmail.com \
--cc=perex@perex.cz \
--cc=peron.clem@gmail.com \
--cc=samuel@sholland.org \
--cc=tiwai@suse.com \
--cc=wens@csie.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 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.