From: Frank Li <Frank.li@nxp.com>
To: Daniel Baluta <daniel.baluta@gmail.com>
Cc: Laurentiu Mihalcea <laurentiumihalcea111@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Daniel Baluta <daniel.baluta@nxp.com>,
Mark Brown <broonie@kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Takashi Iwai <tiwai@suse.com>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
Jaroslav Kysela <perex@perex.cz>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-sound@vger.kernel.org, imx@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/5] ASoC: SOF: imx: add driver for imx95
Date: Wed, 18 Dec 2024 12:06:16 -0500 [thread overview]
Message-ID: <Z2MBCPP4G055Jbbs@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <CAEnQRZArKSOtka46A_SOiV2=8bs9B36ubAJM3GqYJZkKyBt_4A@mail.gmail.com>
On Wed, Dec 18, 2024 at 03:01:11PM +0200, Daniel Baluta wrote:
> > >>> Frank
> > >> the SOF drivers do indeed have some similarities, but each of them has their own quirks which IMO makes it a bit harder to add the 95 support. We need to figure out the common parts and then move them to imx-common, but I believe this can be solved incrementally.
> > > You should create common part firstly, then implement equal function with
> > > existed part. Finially add imx95 part.
> > >
> > > Frank
> >
> > Yes, I'm aware of how this _should_ be done, but, like I mentioned, the change is not trivial and will
> > require tweaking the other drivers as well. As such, I'd like to get the 95 support in as-is firstly.
> >
> > Are there any other thoughts on this?
>
> Laurentiu, Frank please trim the emails and keep only the relevant
> part for discussion.
>
> As for this matter I think we should go with the current version Laurentiu sent.
>
> It is inline with the implementation for imx8qxp, imx8qm, imx8mp and
> imx8ulp which we already have upstream.
>
> There is always space for refactorization and improvements. The
> current version of the code
> is simple enough to go in as it is.
Need provide enough reason in commit message show why need create new one,
and but not reused existed one, which help maintainer and reviewer to judge
if it make sense.
Frank
>
> With this,
>
> Reviewed-by: Daniel Baluta <daniel.baluta@nxp.com>
>
> thanks,
> Daniel.
next prev parent reply other threads:[~2024-12-18 17:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 19:52 [PATCH v2 0/5] add sof support on imx95 Laurentiu Mihalcea
2024-11-13 19:52 ` [PATCH v2 1/5] ASoC: dt-bindings: add common binding for NXP CPUs Laurentiu Mihalcea
2024-11-13 20:03 ` Frank Li
2024-11-15 17:33 ` Rob Herring
2024-11-13 19:52 ` [PATCH v2 2/5] ASoC: dt-bindings: add binding for imx95's CM7 core Laurentiu Mihalcea
2024-11-13 20:07 ` Frank Li
2024-11-13 19:52 ` [PATCH v2 3/5] ASoC: dt-bindings: audio-graph-card2: add widgets and hp-det-gpios support Laurentiu Mihalcea
2024-11-13 20:11 ` Frank Li
2024-12-12 9:59 ` Laurentiu Mihalcea
2024-12-13 0:40 ` Kuninori Morimoto
2024-11-13 19:52 ` [PATCH v2 4/5] ASoC: SOF: imx: add driver for imx95 Laurentiu Mihalcea
2024-11-13 20:17 ` Frank Li
2024-12-12 11:11 ` Laurentiu Mihalcea
2024-12-12 15:13 ` Frank Li
2024-12-16 12:23 ` Laurentiu Mihalcea
2024-12-18 13:01 ` Daniel Baluta
2024-12-18 17:06 ` Frank Li [this message]
2024-11-13 19:52 ` [PATCH v2 5/5] arm64: dts: imx: add imx95 dts for sof Laurentiu Mihalcea
2024-11-13 20:21 ` Frank Li
2024-12-12 10:04 ` Laurentiu Mihalcea
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=Z2MBCPP4G055Jbbs@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=broonie@kernel.org \
--cc=daniel.baluta@gmail.com \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurentiumihalcea111@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
--cc=tiwai@suse.com \
--cc=yung-chuan.liao@linux.intel.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