From: Xingyu Wu <xingyu.wu@starfivetech.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Claudiu Beznea <Claudiu.Beznea@microchip.com>,
Jaroslav Kysela <perex@perex.cz>, "Takashi Iwai" <tiwai@suse.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor.dooley@microchip.com>,
Walker Chen <walker.chen@starfivetech.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<alsa-devel@alsa-project.org>, <linux-sound@vger.kernel.org>
Subject: Re: [PATCH v1 2/2] ASoC: starfive: Add drivers of Cadence Multi-Channel I2S Controller
Date: Fri, 22 Dec 2023 17:11:17 +0800 [thread overview]
Message-ID: <c94b377a-1e21-4361-ae82-ca84d1dce60a@starfivetech.com> (raw)
In-Reply-To: <861f9b28-863d-48b0-8491-add4a286597e@sirena.org.uk>
On 2023/12/21 20:55, Mark Brown wrote:
> On Thu, Dec 21, 2023 at 11:32:23AM +0800, Xingyu Wu wrote:
>
>> sound/soc/starfive/cdns-jh8100-i2s-pcm.c | 262 ++++++++
>> sound/soc/starfive/cdns-jh8100-i2s.c | 727 +++++++++++++++++++++++
>> sound/soc/starfive/cdns-jh8100-i2s.h | 171 ++++++
>
> If this is a Cadence IP why is the entire driver SoC specific?
This a new driver about this Cadence I2S controller. Should I create a new folder and file like this:
sound/soc/cdns/cdns-i2s*
and I use different compatible to support other SoC like JH8100?
Best regards,
Xingyu Wu
next prev parent reply other threads:[~2023-12-22 9:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 3:32 [PATCH v1 0/2] Add Cadence I2S controller driver for the Xingyu Wu
2023-12-21 3:32 ` [PATCH v1 1/2] dt-bindings: ASoC: Add Cadence I2S controller for StarFive JH8100 SoC Xingyu Wu
2023-12-21 13:53 ` Conor Dooley
2023-12-21 13:58 ` Mark Brown
2023-12-22 9:55 ` Xingyu Wu
2023-12-22 13:03 ` Mark Brown
2023-12-29 8:30 ` Xingyu Wu
2023-12-22 9:44 ` Xingyu Wu
2023-12-21 16:07 ` Krzysztof Kozlowski
2023-12-22 9:56 ` Xingyu Wu
2023-12-21 3:32 ` [PATCH v1 2/2] ASoC: starfive: Add drivers of Cadence Multi-Channel I2S Controller Xingyu Wu
2023-12-21 12:55 ` Mark Brown
2023-12-22 9:11 ` Xingyu Wu [this message]
2023-12-22 12:39 ` Mark Brown
2023-12-29 8:31 ` Xingyu Wu
2023-12-22 21:32 ` kernel test robot
2023-12-23 11:54 ` kernel test robot
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=c94b377a-1e21-4361-ae82-ca84d1dce60a@starfivetech.com \
--to=xingyu.wu@starfivetech.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.com \
--cc=walker.chen@starfivetech.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;
as well as URLs for NNTP newsgroup(s).