alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Vedang Patel <vedang.patel@intel.com>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>, alsa-devel@alsa-project.org
Cc: vinod.koul@intel.com, jeeja.kp@intel.com, marc.herbert@intel.com,
	subhransu.s.prusty@intel.com, liam.r.girdwood@intel.com
Subject: Re: [PATCH 1/3] ASoC: hdac_hdmi: Increase loglevel of hex dump printed
Date: Thu, 14 Apr 2016 08:15:50 -0700	[thread overview]
Message-ID: <1460646950.10382.1.camel@intel.com> (raw)
In-Reply-To: <570D9C3D.5060407@sakamocchi.jp>

On Wed, 2016-04-13 at 10:09 +0900, Takashi Sakamoto wrote:
> Hi,
> 
> On Apr 13 2016 07:08, vedang.patel@intel.com wrote:
> > From: Vedang Patel <vedang.patel@intel.com>
> > 
> > The hdac_hdmi codec driver prints the ELD information everytime an
> > external monitor is connected. Make it so that the information is
> > only
> > printed when someone trying to debug the driver explicitly enables
> > it.
> 
> For this purpose, I think it better to use Linux tracing framework, 
> instead of such an ancient fashion. The type of '__dynamic_array' is 
> suitable for your aim.
> 
> As a quick glance of ASOC, there're several usage of the framework
> (see 
> include/trace/events/asoc.h). So overall, I believe it's OK to use
> the 
> framework.
> 
> I also have the same advice for your patch 3/3.
> 

Thanks Takashi for the input. I will work on it and send out the new
patches soon.

-Vedang

> > print_hex_dump uses printk(KERN_DEBUG,... which is different from
> > dev_dbg used elsewhere in the driver: it's always enabled at
> > compile-time. Add #ifdef DEBUG condition for logging consistency.
> > 
> > Signed-off-by: Vedang Patel <vedang.patel@intel.com>
> > ---
> >   sound/soc/codecs/hdac_hdmi.c | 2 ++
> >   1 file changed, 2 insertions(+)
> > 
> > diff --git a/sound/soc/codecs/hdac_hdmi.c
> > b/sound/soc/codecs/hdac_hdmi.c
> > index aaa038f..653fd9e 100644
> > --- a/sound/soc/codecs/hdac_hdmi.c
> > +++ b/sound/soc/codecs/hdac_hdmi.c
> > @@ -1066,8 +1066,10 @@ static void hdac_hdmi_present_sense(struct
> > hdac_hdmi_pin *pin, int repoll)
> >   				snd_jack_report(pcm->jack,
> > SND_JACK_AVOUT);
> >   			}
> > 
> > +#ifdef DEBUG
> >   			print_hex_dump_bytes("ELD: ",
> > DUMP_PREFIX_OFFSET,
> >   					pin->eld.eld_buffer, pin
> > ->eld.eld_size);
> > +#endif
> >   		} else {
> >   			pin->eld.monitor_present = false;
> >   			pin->eld.eld_valid = false;
> 
> 
> Regards
> 
> Takashi Sakamoto

  reply	other threads:[~2016-04-14 15:15 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12 22:08 [PATCH 0/3] ASoC: Reduce audio related kernel spew vedang.patel
2016-04-12 22:08 ` [PATCH 1/3] ASoC: hdac_hdmi: Increase loglevel of hex dump printed vedang.patel
2016-04-13  1:09   ` Takashi Sakamoto
2016-04-14 15:15     ` Vedang Patel [this message]
2016-04-15 19:13       ` Vedang Patel
2016-04-12 22:08 ` [PATCH 2/3] ASoC: Intel: common: increase the loglevel of "FW Poll Status" vedang.patel
2016-06-27 16:40   ` Applied "ASoC: Intel: common: increase the loglevel of "FW Poll Status"." to the asoc tree Mark Brown
2016-04-12 22:08 ` [PATCH 3/3] ASoC: Intel: Skylake: Increase loglevel of debug messages vedang.patel
2016-04-26 23:03   ` [PATCH v2 0/3] ASoC: Reduce audio related kernel spew vedang.patel
2016-04-26 23:03     ` [PATCH v2 1/3] ASoC: hdac_hdmi: Increase loglevel of hex dump printed vedang.patel
2016-04-26 23:03     ` [PATCH v2 2/3] ASoC: Intel: common: increase the loglevel of "FW Poll Status" vedang.patel
2016-04-26 23:03     ` [PATCH v2 3/3] ASoC: Intel: Skylake: Increase loglevel of debug messages vedang.patel
2016-06-01  1:14       ` [PATCH v3 0/3] ASoC: Reduce audio related kernel spew vedang.patel
2016-06-01  1:14         ` [PATCH v3 1/3] ASoC: hdac_hdmi: Increase loglevel of hex dump printed vedang.patel
2016-06-27 16:40           ` Applied "ASoC: hdac_hdmi: Increase loglevel of hex dump printed" to the asoc tree Mark Brown
2016-06-01  1:15         ` [PATCH v3 2/3] ASoC: Intel: common: increase the loglevel of "FW Poll Status" vedang.patel
2016-06-01  1:15         ` [PATCH v3 3/3] ASoC: Intel: Skylake: Increase loglevel of debug messages vedang.patel
2016-06-01  5:56         ` [PATCH v3 0/3] ASoC: Reduce audio related kernel spew Vinod Koul
2016-06-25  0:37       ` [REPOST REPOST PATCH " vedang.patel
2016-06-25  0:37         ` [REPOST REPOST PATCH v3 1/3] ASoC: hdac_hdmi: Increase loglevel of hex dump printed vedang.patel
2016-06-25  0:37         ` [REPOST REPOST PATCH v3 2/3] ASoC: Intel: common: increase the loglevel of "FW Poll Status" vedang.patel
2016-06-25  0:37         ` [REPOST REPOST PATCH v3 3/3] ASoC: Intel: Skylake: Increase loglevel of debug messages vedang.patel
2016-06-27 14:50         ` [REPOST REPOST PATCH v3 0/3] ASoC: Reduce audio related kernel spew Mark Brown
2016-06-29 23:39           ` Patel, Vedang
2016-06-30  2:27             ` Vinod Koul
2016-07-01  7:50               ` Mark Brown
2016-06-27 16:40       ` Applied "ASoC: Intel: Skylake: Increase loglevel of debug messages." to the asoc tree 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=1460646950.10382.1.camel@intel.com \
    --to=vedang.patel@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=jeeja.kp@intel.com \
    --cc=liam.r.girdwood@intel.com \
    --cc=marc.herbert@intel.com \
    --cc=o-takashi@sakamocchi.jp \
    --cc=subhransu.s.prusty@intel.com \
    --cc=vinod.koul@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 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).