From: Eugeniu Rosca <erosca@de.adit-jv.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
<linux-sound@vger.kernel.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Charles Keepax <ckeepax@opensource.cirrus.com>,
Vincenzo De Michele <vincenzo.michele@davinci.de>,
Dean Jenkins <dean.jenkins@siemens.com>,
Andreas Pape <Andreas.Pape4@bosch.com>,
Yeswanth Rayapati <yeswanth.rayapati@in.bosch.com>,
Eugeniu Rosca <erosca@de.adit-jv.com>,
Eugeniu Rosca <eugeniu.rosca@bosch.com>,
Eugeniu Rosca <roscaeugeniu@gmail.com>
Subject: Re: [PATCH] ASoC: rcar: adg: correct TIMSEL setting for SSI9
Date: Fri, 1 Mar 2024 09:58:15 +0100 [thread overview]
Message-ID: <20240301085815.GA3088@mypc> (raw)
In-Reply-To: <8734tc86ra.wl-kuninori.morimoto.gx@renesas.com>
Hello Morimoto-san,
On Thu, Feb 29, 2024 at 12:16:09AM +0000, Kuninori Morimoto wrote:
> > > A number of concerns have been raised internally, related to the fact
> > > that the "optimized/simplified" counter-proposal behaves differently
> > > depending on the value returned by rsnd_ssi_is_pin_sharing().
> (snip)
> > Could you please indicate the sample case of differently behaves ?
> > For example, if xxx was xxx, original code behaves xxx, but simple
> > code behaves xxx, etc. I'm not sure what is your concern...
>
> Ah.., in case of SSI8.
>
> > > While it may be clear for you that pin sharing is mandatory, it is not
> > > immediately obvious to the casual reader/contributor purely based on
> > > code review.
>
> SSI8 with pin sharing is not only this function issue,
> you can see same comment on rsnd_adg_set_ssi_clk().
> # It is not clear for me either, I have been forgot about it :)
> # and I have never use SSI8 before, so I'm not sure what happen
> # if someone use it
>
> If you have concern about it, why don't you add such error/message
> when begining time, instead of each functions ?
> Because of compatibility, rsnd_ssi_probe() is not good place,
> so I think rsnd_ssi_connect() is good place.
Thanks for your patience and for accepting different viewpoints,
while discussing the issue. Please, kindly review v2:
https://lore.kernel.org/linux-sound/20240301085003.3057-1-erosca@de.adit-jv.com
BR, Eugeniu
prev parent reply other threads:[~2024-03-01 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 16:35 [PATCH] ASoC: rcar: adg: correct TIMSEL setting for SSI9 Eugeniu Rosca
2024-02-25 23:21 ` Kuninori Morimoto
2024-02-27 12:07 ` Eugeniu Rosca
2024-02-27 23:22 ` Kuninori Morimoto
2024-02-28 9:45 ` Eugeniu Rosca
2024-02-28 23:36 ` Kuninori Morimoto
2024-02-29 0:16 ` Kuninori Morimoto
2024-03-01 8:58 ` Eugeniu Rosca [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=20240301085815.GA3088@mypc \
--to=erosca@de.adit-jv.com \
--cc=Andreas.Pape4@bosch.com \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=dean.jenkins@siemens.com \
--cc=eugeniu.rosca@bosch.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=roscaeugeniu@gmail.com \
--cc=tiwai@suse.com \
--cc=vincenzo.michele@davinci.de \
--cc=wsa+renesas@sang-engineering.com \
--cc=yeswanth.rayapati@in.bosch.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox