From: Daniel Mack <zonque@gmail.com>
To: "jonsmirl@gmail.com" <jonsmirl@gmail.com>
Cc: alsa-devel mailing list <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
lgirdwood@gmail.com
Subject: Re: [PATCH] ALSA: ASoC: add codec driver for TI TAS5086
Date: Wed, 22 May 2013 19:55:22 +0200 [thread overview]
Message-ID: <519D068A.8030003@gmail.com> (raw)
In-Reply-To: <CAKON4OyqoUTsYHqv3kW3jN9Za=-Z866rcjPiANL8t5uyraK=6w@mail.gmail.com>
On 22.05.2013 19:50, jonsmirl@gmail.com wrote:
> On Fri, Mar 8, 2013 at 6:07 AM, Daniel Mack <zonque@gmail.com> wrote:
>> This patch adds a driver for TI's TA5086 6-channel PWM processor.
>>
>> This chip has a very unusual register layout, specifically because the
>> registers are of unequal size, and multi-byte registers require bulk
>> writes to take effect. Regmap does not support these kind of mappings.
>>
>> Currently, the driver does not touch any of the registers >= 0x20, so
>> it doesn't matter, because the register map is mapped to an 8-bit array.
>> In case more features will be added in the future that require access
>> to higher registers, the entire regmap H/W I/O routines have to be
>> open-coded.
>
> Check out my tas5504 driver from a long time ago. It dealt with those registers.
>
> https://github.com/jonsmirl/mpc5200/blob/master/sound/soc/codecs/tas5504.c
> https://github.com/jonsmirl/mpc5200/blob/master/sound/soc/codecs/tas5504.h
Sure, without any regmap abstractions, things are somehow manageable.
Though you lose all the nice things that regmap gives you, such as
hardware independence and caching. I might have a different solution,
but I need to get my hands on one of these devices to test.
On a slightly different note: why isn't your driver in the mainline kernel?
Thanks,
Daniel
next prev parent reply other threads:[~2013-05-22 17:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 11:07 [PATCH] ALSA: ASoC: add codec driver for TI TAS5086 Daniel Mack
2013-03-08 11:42 ` Mark Brown
2013-03-08 12:26 ` Daniel Mack
2013-03-08 12:30 ` Mark Brown
2013-03-08 12:31 ` Daniel Mack
2013-05-22 17:50 ` jonsmirl
2013-05-22 17:55 ` Daniel Mack [this message]
2013-05-22 18:01 ` jonsmirl
2013-05-22 18:20 ` jonsmirl
2013-05-22 18:24 ` jonsmirl
2013-05-22 18:25 ` Daniel Mack
2013-05-22 18:33 ` jonsmirl
2013-05-22 18:36 ` Daniel Mack
2013-05-22 19:31 ` 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=519D068A.8030003@gmail.com \
--to=zonque@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jonsmirl@gmail.com \
--cc=lgirdwood@gmail.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).