From: Maxime Ripard <maxime.ripard@bootlin.com>
To: "Clément Péron" <peron.clem@gmail.com>
Cc: devicetree <devicetree@vger.kernel.org>,
Linux-ALSA <alsa-devel@alsa-project.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-sunxi <linux-sunxi@googlegroups.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Takashi Iwai <tiwai@suse.com>,
Chen-Yu Tsai <wens@csie.org>, Mark Brown <broonie@kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 2/5] ASoC: sun4i-spdif: Add support for H6 SoC
Date: Fri, 3 May 2019 16:54:35 +0200 [thread overview]
Message-ID: <20190503145435.jziomr3sqxp6jbpd@flea> (raw)
In-Reply-To: <CAJiuCcdFUPBsXfKtDLt-p6Edx-7JrST9d0C=ofCU4CL8ZxwcsA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2071 bytes --]
On Thu, May 02, 2019 at 11:39:24AM +0200, Clément Péron wrote:
> > > @@ -169,16 +181,25 @@ struct sun4i_spdif_dev {
> > > struct snd_soc_dai_driver cpu_dai_drv;
> > > struct regmap *regmap;
> > > struct snd_dmaengine_dai_dma_data dma_params_tx;
> > > + const struct sun4i_spdif_quirks *quirks;
> >
> > I guess this will generate a warning since the structure hasn't been
> > defined yet?
>
> It's a pointer to a structure so no warning from the compiler.
Damn, I was convinced just declaring a pointer to a structure would
result to a gcc warning. Nevermind then.
> > > @@ -405,22 +426,26 @@ static struct snd_soc_dai_driver sun4i_spdif_dai = {
> > > .name = "spdif",
> > > };
> > >
> > > -struct sun4i_spdif_quirks {
> > > - unsigned int reg_dac_txdata; /* TX FIFO offset for DMA config */
> > > - bool has_reset;
> > > -};
> > > -
> > > static const struct sun4i_spdif_quirks sun4i_a10_spdif_quirks = {
> > > .reg_dac_txdata = SUN4I_SPDIF_TXFIFO,
> > > + .reg_fctl_ftx = SUN4I_SPDIF_FCTL_FTX,
> > > };
> > >
> > > static const struct sun4i_spdif_quirks sun6i_a31_spdif_quirks = {
> > > .reg_dac_txdata = SUN4I_SPDIF_TXFIFO,
> > > + .reg_fctl_ftx = SUN4I_SPDIF_FCTL_FTX,
> > > .has_reset = true,
> > > };
> > >
> > > static const struct sun4i_spdif_quirks sun8i_h3_spdif_quirks = {
> > > .reg_dac_txdata = SUN8I_SPDIF_TXFIFO,
> > > + .reg_fctl_ftx = SUN4I_SPDIF_FCTL_FTX,
> > > + .has_reset = true,
> > > +};
> > >
> > > +static const struct sun4i_spdif_quirks sun50i_h6_spdif_quirks = {
> > > + .reg_dac_txdata = SUN8I_SPDIF_TXFIFO,
> > > + .reg_fctl_ftx = SUN50I_H6_SPDIF_FCTL_FTX,
> > > .has_reset = true,
> >
> > The reg_dac_txdata and reg_fctl_ftx changes here should also be part
> > of a separate patch.
>
> You mean the reg_fctl_ftx quirk and the H6 introduction should be split ?
Yep
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2019-05-03 14:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 19:17 [PATCH v2 0/5] Allwinner H6 SPDIF support Clément Péron
[not found] ` <20190419191730.9437-1-peron.clem-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-04-19 19:17 ` [PATCH v2 1/5] dt-bindings: sound: sun4i-spdif: Add Allwinner H6 compatible Clément Péron
2019-05-01 19:50 ` Rob Herring
2019-05-01 21:52 ` Rob Herring
2019-05-02 8:20 ` Maxime Ripard
2019-04-19 19:17 ` [PATCH v2 2/5] ASoC: sun4i-spdif: Add support for H6 SoC Clément Péron
[not found] ` <20190419191730.9437-3-peron.clem-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-05-02 8:25 ` Maxime Ripard
2019-05-02 9:39 ` Clément Péron
2019-05-03 14:54 ` Maxime Ripard [this message]
2019-04-19 19:17 ` [PATCH v2 3/5] arm64: dts: allwinner: Add SPDIF node for Allwinner H6 Clément Péron
2019-04-19 19:17 ` [PATCH v2 4/5] arm64: dts: allwinner: h6: Enable SPDIF for Beelink GS1 Clément Péron
2019-04-19 19:17 ` [PATCH v2 5/5] arm64: defconfig: Enable Sun4i SPDIF module Clément Péron
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=20190503145435.jziomr3sqxp6jbpd@flea \
--to=maxime.ripard@bootlin.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=peron.clem@gmail.com \
--cc=robh+dt@kernel.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 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).