From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: Code Kipper <codekipper@gmail.com>,
"Mailing List, Arm" <linux-arm-kernel@lists.infradead.org>,
linux-sunxi <linux-sunxi@googlegroups.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
alsa-devel@alsa-project.org, be17068@iperbole.bo.it
Subject: Re: [linux-sunxi] [PATCH 2/2] ASoC: sunxi: compatibility for sun6i to SPDIF
Date: Sat, 30 Jul 2016 17:21:53 +0200 [thread overview]
Message-ID: <20160730152153.GV6215@lukather> (raw)
In-Reply-To: <CAGRGNgU-7skLeRNOxfVpqNXSaLTLA+vAZrm8=sdo0NJLbopJ7Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1930 bytes --]
On Sun, Jul 31, 2016 at 12:40:48AM +1000, Julian Calaby wrote:
> Hi Marcus,
>
> On Sun, Jul 31, 2016 at 12:27 AM, <codekipper@gmail.com> wrote:
> > From: Marcus Cooper <codekipper@gmail.com>
> >
> > The A31 SoC uses the same SPDIF block as found in earlier SoCs, but its
> > reset is controlled via a separate reset controller.
> >
> > The DMA also complains when the maxburst is set to 4 so it's been adjusted
> > to 8 which suites both the older and newer SoCs.
> >
> > Signed-off-by: Marcus Cooper <codekipper@gmail.com>
> > ---
> > sound/soc/sunxi/sun4i-spdif.c | 17 ++++++++++++++++-
> > 1 file changed, 16 insertions(+), 1 deletion(-)
> >
> > diff --git a/sound/soc/sunxi/sun4i-spdif.c b/sound/soc/sunxi/sun4i-spdif.c
> > index 0b04fb0..88fbb3a 100644
> > --- a/sound/soc/sunxi/sun4i-spdif.c
> > +++ b/sound/soc/sunxi/sun4i-spdif.c
> > @@ -482,11 +485,23 @@ static int sun4i_spdif_probe(struct platform_device *pdev)
> > }
> >
> > host->dma_params_tx.addr = res->start + SUN4I_SPDIF_TXFIFO;
> > - host->dma_params_tx.maxburst = 4;
> > + host->dma_params_tx.maxburst = 8;
> > host->dma_params_tx.addr_width = DMA_SLAVE_BUSWIDTH_2_BYTES;
> >
> > platform_set_drvdata(pdev, host);
> >
> > + if (of_device_is_compatible(pdev->dev.of_node,
> > + "allwinner,sun6i-a31-spdif")) {
>
> Given how much Allwinner likes to shuffle stuff around with each SoC
> generation, would it make sense to add a flag for this in some
> compatible specific config structure instead of checking against the
> compatible?
It really depends on the size of the quirks you have to maintain. If
it's just a single one like here, I'd say it's less of a hassle (and
actually easier and conciser to implement).
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-30 15:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 14:27 [PATCH 0/2] ASoC: Extended SPDIF support to Allwinner A31 SoCs codekipper
2016-07-30 14:27 ` [PATCH 1/2] ASoC: sunxi: Add bindings for sun6i to SPDIF codekipper
2016-07-30 15:17 ` Maxime Ripard
2016-07-30 15:34 ` Code Kipper
2016-07-30 15:40 ` Maxime Ripard
2016-07-30 14:27 ` [PATCH 2/2] ASoC: sunxi: compatibility " codekipper
2016-07-30 14:40 ` [linux-sunxi] " Julian Calaby
2016-07-30 15:21 ` Maxime Ripard [this message]
2016-07-30 15:19 ` Maxime Ripard
[not found] ` <170941469890365@web9j.yandex.ru>
2016-07-30 15:20 ` maxime.ripard
2016-08-01 13:39 ` [linux-sunxi] " Chen-Yu Tsai
2016-08-22 16:04 ` Maxime Ripard
2016-08-12 12:29 ` Applied "ASoC: sunxi: compatibility for sun6i to SPDIF" to the asoc tree 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=20160730152153.GV6215@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=alsa-devel@alsa-project.org \
--cc=be17068@iperbole.bo.it \
--cc=broonie@kernel.org \
--cc=codekipper@gmail.com \
--cc=julian.calaby@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.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