All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Hsu <KCHSU0@nuvoton.com>
To: broonie@kernel.org, lgirdwood@gmail.com
Cc: alsa-devel@alsa-project.org, anatol.pomozov@gmail.com,
	benzh@chromium.org, YHCHuang@nuvoton.com, CTLIN0@nuvoton.com,
	yong.zhi@intel.com
Subject: Re: [PATCH] ASoC: nau8825: Modify power management and add interrupt wakeup
Date: Thu, 25 Feb 2016 07:09:47 +0800	[thread overview]
Message-ID: <56CE383B.4050306@nuvoton.com> (raw)
In-Reply-To: <d255aac675d4418c87af834edc567021@NTHCML01B.nuvoton.com>

Hi Mark,
This patch has cancel and only submit enhance codec suspend and resume 
patch.
Please review the following link for the patch. Many thanks.

http://mailman.alsa-project.org/pipermail/alsa-devel/2016-January/102924.html
[alsa-devel] [PATCH] ASoC: nau8825: fix interrupt fails and unstable 
after resume

On 1/8/2016 9:14 PM, Mark Brown wrote:
> On Fri, Jan 08, 2016 at 03:11:22PM +0800, John Hsu wrote:
>   
>> 1. Enhance codec suspend and resume sequence 2. Add interrupt wakeup 
>> function
>>     
>
> If this is two or more separate changes you should be sending two or more separate patches.  You also need a better changelog which describes what the patch is supposed to do, in what way is suspend and resume enhanced for example?
>
>   
>> +/**
>> + * nau8825_init_wakeup - set wakeup capability for codec
>> + *
>> + * @codec:  codec device component
>> + *
>> + * After this function done, codec can support system wakeup by button.
>> + */
>> +int nau8825_init_wakeup(struct snd_soc_codec *codec) {
>> +	struct nau8825 *nau8825 = snd_soc_codec_get_drvdata(codec);
>> +
>> +	device_init_wakeup(nau8825->dev, true);
>> +
>> +	return 0;
>> +}
>> +EXPORT_SYMBOL_GPL(nau8825_init_wakeup);
>>     
>
> You need a bit more explanation as to what's going on here.  Why is this not something the driver just does or if this should be done elsewhere why do we need the wrapper function?
>
>   
>> +int nau8825_irq_wakeup(struct snd_soc_codec *codec, int on) {
>> +	struct nau8825 *nau8825 = snd_soc_codec_get_drvdata(codec);
>>     
>
> Same thing here, this looks like an unclear interface.
>   

  parent reply	other threads:[~2016-02-24 23:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-08  7:11 [PATCH] ASoC: nau8825: Modify power management and add interrupt wakeup John Hsu
2016-01-08 13:13 ` Mark Brown
     [not found]   ` <d255aac675d4418c87af834edc567021@NTHCML01B.nuvoton.com>
2016-02-24 23:09     ` John Hsu [this message]
2016-02-25  1:55       ` Mark Brown
2016-02-25 17:36         ` John Hsu

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=56CE383B.4050306@nuvoton.com \
    --to=kchsu0@nuvoton.com \
    --cc=CTLIN0@nuvoton.com \
    --cc=YHCHuang@nuvoton.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=anatol.pomozov@gmail.com \
    --cc=benzh@chromium.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=yong.zhi@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.