From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: johnnyhsu@realtek.com
Cc: alsa-devel@alsa-project.org, flove@realtek.com, lrg@slimlogic.co.uk
Subject: Re: [PATCH] ASoC: Add driver for rt5631
Date: Tue, 6 Sep 2011 11:05:05 -0700 [thread overview]
Message-ID: <20110906180501.GD2924@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1315305162-18206-1-git-send-email-johnnyhsu@realtek.com>
On Tue, Sep 06, 2011 at 06:32:42PM +0800, johnnyhsu@realtek.com wrote:
> switch (reg) {
> - case RT5631_VENDOR_ID:
> - case RT5631_VENDOR_ID1:
> - case RT5631_VENDOR_ID2:
> - return 0;
> - default:
> + case RT5631_RESET:
> + case RT5631_INT_ST_IRQ_CTRL_2:
> + case RT5631_INDEX_ADD:
> + case RT5631_INDEX_DATA:
> + case RT5631_EQ_CTRL:
> return 1;
> + default:
> + return 0;
This is an incremental patch against your previous driver, not a full
patch. You should always send a patches which can be applied against
current kernels.
> - pr_info("enter %s, syclk=%d\n", __func__, freq);
> + dev_info(codec->dev, "enter %s, syclk=%d\n", __func__, freq);
This should be a debug level print at most, otherwise you just spam the
console.
> if (!freq_in || !freq_out) {
> dev_dbg(codec->dev, "PLL disabled\n");
> - return -EINVAL;
> + return 0;
I'd expect to see some sort of register write when the PLL is disabled?
> /**
> - * rt5631_index_reg_show - sysfs file for dumping index registers of 2nd layer
> + * rt5631_index_reg_show: Show private register of rt5631 codec.
> + * @dev: device to query.
> + * @attr: device attribute.
> + * @buf: buffer to display.
> + *
> + * To show private registers which are not changed often by user.
> + * You have to access them through register 0x6a and 0x6c.
> */
> static ssize_t rt5631_index_reg_show(struct device *dev,
> struct device_attribute *attr, char *buf)
As I've told you repeatedly you should be using the standard facilities
for debug access to registers - you should not open coding this in your
driver. Once again, ignoring review comments isn't helpful.
next parent reply other threads:[~2011-09-06 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1315305162-18206-1-git-send-email-johnnyhsu@realtek.com>
2011-09-06 18:05 ` Mark Brown [this message]
[not found] <1315365395-19945-1-git-send-email-johnnyhsu@realtek.com>
2011-09-21 14:55 ` [PATCH] ASoC: Add driver for rt5631 Mark Brown
[not found] ` <76636494E6524EFCACC65A52F218E03B@realtek.com.tw>
2011-09-23 10:49 ` 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=20110906180501.GD2924@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=flove@realtek.com \
--cc=johnnyhsu@realtek.com \
--cc=lrg@slimlogic.co.uk \
/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).