From: Mark Brown <broonie@kernel.org>
To: Bard Liao <bardliao@realtek.com>
Cc: Oder Chiou <oder_chiou@realtek.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lars@metafoo.de" <lars@metafoo.de>,
"zhengxing@rock-chips.com" <zhengxing@rock-chips.com>,
"yang.a.fang@intel.com" <yang.a.fang@intel.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
John Lin <john.lin@realtek.com>,
"koro.chen@mediatek.com" <koro.chen@mediatek.com>,
Flove <flove@realtek.com>
Subject: Re: [PATCH 1/2] ASoC: rt5645: Adds push button support for rt5650
Date: Wed, 22 Apr 2015 12:04:13 +0100 [thread overview]
Message-ID: <20150422110413.GR22845@sirena.org.uk> (raw)
In-Reply-To: <ABFD875FF5FB574BA706497D987D48D701062EE9@RTITMBSV03.realtek.com.tw>
[-- Attachment #1.1: Type: text/plain, Size: 1237 bytes --]
On Tue, Apr 21, 2015 at 11:41:48AM +0000, Bard Liao wrote:
> > OK, you probaly want to move to separate default tables per device.
> > This is something that should have been called out in the commit log.
> Do you mean we need to write it down in the commit log and send
> another patch to use separate default tables for different device?
Yes, that's fine.
> Regarding the different default tables, do you mean something like:
> case RT5645_DEVICE_ID:
> rt5645->codec_type = CODEC_TYPE_RT5645;
> dev_info(&i2c->dev, "Codec type is: RT5645\n");
> + rt5645_regmap. reg_defaults = rt5645_reg;
> break;
> case RT5650_DEVICE_ID:
> rt5645->codec_type = CODEC_TYPE_RT5650;
> dev_info(&i2c->dev, "Codec type is: RT5650\n");
> + rt5645_regmap. reg_defaults = rt5650_reg;
> break;
It'd be better to have different regmap_config structures rather than
changing the register defaults in the one structure but basically yes.
> > OK, can we have a comment for that please? We might want to extend
> > this in the future as the userspace ABI grows richer (and depending on
> > how things get reported we may need to synthesize at least a double press
> > for userspace).
> Do you mean comment in the source code?
Yes, please.
[-- 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-04-22 11:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 2:37 [PATCH 1/2] ASoC: rt5645: Adds push button support for rt5650 Bard Liao
2015-04-20 2:37 ` [PATCH 2/2] ASoC: Intel: rt5645_set_jack_detect is changed Bard Liao
2015-04-20 20:57 ` Mark Brown
2015-04-20 20:41 ` [PATCH 1/2] ASoC: rt5645: Adds push button support for rt5650 Mark Brown
2015-04-21 2:08 ` Bard Liao
2015-04-21 10:48 ` Mark Brown
2015-04-21 11:41 ` Bard Liao
2015-04-22 11:04 ` 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=20150422110413.GR22845@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=flove@realtek.com \
--cc=john.lin@realtek.com \
--cc=koro.chen@mediatek.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=oder_chiou@realtek.com \
--cc=yang.a.fang@intel.com \
--cc=zhengxing@rock-chips.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