From: Mark Brown <broonie@kernel.org>
To: maruthi srinivas <maruthi.srinivas.b@gmail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Bayyavarapu, Maruthi" <maruthi.bayyavarapu@amd.com>,
Takashi Iwai <tiwai@suse.de>, Liam Girdwood <lgirdwood@gmail.com>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
Alex Deucher <alexander.deucher@amd.com>,
Alex Deucher <alexdeucher@gmail.com>,
Dave Airlie <airlied@gmail.com>
Subject: Re: [PATCH V5 3/3] ASoC: AMD: add AMD ASoC ACP-I2S driver
Date: Tue, 25 Aug 2015 19:32:58 +0100 [thread overview]
Message-ID: <20150825183258.GL12878@sirena.org.uk> (raw)
In-Reply-To: <CANv6ZMaQV5XK3RG28ayeX-QsC2F3x+sK8ouegFgT=_xM+GUSFg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2161 bytes --]
On Tue, Aug 25, 2015 at 03:26:54PM +0530, maruthi srinivas wrote:
> On Tue, Aug 25, 2015 at 11:36 AM, Mark Brown <broonie@kernel.org> wrote:
> > Please explain this in more detail, shared register ranges are very
> > common and are the sort of things MFDs are supposed to help with.
> In our case, ACP I2S driver need not do a 'devm_ioremap_resource' to
> get mmio base.
That sounds like a MFD type problem...
> ACP audio IP (DMA + I2S+ Others) registers can be accessed, using
> GPU's MMIO base.
> During GPU driver design, it was decided that all the register access
> for entire GPU MMIO
> aperture (includes ACP and others) to be done in GPU module only.
> This is implemented in another patch in this patch series using a
> abstraction layer.
That sounds like converting the Designware driver to use regmap and
providing a regmap would enable code sharing (you can provide a regmap
for accessors if you don't use it in the main driver).
> >> 2. The designware driver depends on the CLKDEV framework which we
> >> don't currently support.
> > You need to support the clock API, it's very easy to do so so there is
> > no excuse for doing something custom here.
> Codec acts as master in our case to provide clock to i2s controller and
> there wasn't a need to use clock APIs unlike in existing designware i2s driver.
> There is no custom implementation.
So you just need to add slave mode support to the driver. Again not a
reason to just copy the code.
> >> 3. Our hardware does not support S16_LE
> > If you have modified the designware IP to remove this support (why would
> > anyone do that?) it's a trivial quirk, if the restriction comes from
> > some other part of the system like the DMA driver then the constraint
> > will come from that part of the system.
> There is a bug in ACP SoC implementation (which combines internal DMA,
> designware I2S
> and other blocks) for 16bit and lower resolution. I felt , it would be
> better to limit functionality
> in I2S DAI capabilities. I will put this limitation in DMA driver
> capabilities, to represent overall
> sound card capabilities, if you suggest.
A quirk would also do the job.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2015-08-25 18:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 21:36 [PATCH V5 3/3] ASoC: AMD: add AMD ASoC ACP-I2S driver Alex Deucher
2015-08-20 23:18 ` Mark Brown
2015-08-20 23:45 ` Alex Deucher
2015-08-21 11:51 ` [alsa-devel] " maruthi srinivas
2015-08-21 16:17 ` Mark Brown
2015-08-24 20:08 ` [alsa-devel] " Alex Deucher
2015-08-25 6:06 ` Mark Brown
2015-08-25 9:56 ` [alsa-devel] " maruthi srinivas
2015-08-25 18:32 ` Mark Brown [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=20150825183258.GL12878@sirena.org.uk \
--to=broonie@kernel.org \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=lgirdwood@gmail.com \
--cc=maruthi.bayyavarapu@amd.com \
--cc=maruthi.srinivas.b@gmail.com \
--cc=tiwai@suse.de \
/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