All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
	alsa-devel@alsa-project.org, broonie@kernel.org
Subject: Re: [PATCH v2] amixer: skip showing asoc tlv byte controls
Date: Thu, 28 Jan 2016 12:10:11 +0530	[thread overview]
Message-ID: <20160128064011.GE11130@localhost> (raw)
In-Reply-To: <s5hy4bameqa.wl-tiwai@suse.de>

On Thu, Jan 28, 2016 at 06:53:49AM +0100, Takashi Iwai wrote:
> On Thu, 28 Jan 2016 05:49:42 +0100,
> Vinod Koul wrote:
> > 
> > ASoC TLV Byte controls are very large size controls so we should add new
> > options for these. So skip dumping contents for these.
> > 
> > $amixer -c0 cget numid=16
> > numid=16,iface=MIXER,name='mdl params'
> >   ; type=BYTES,access=-----RW-,values=30336
> >   : ASoC TLV Byte control, skipping bytes dump
> > 
> > Signed-off-by: Vinod Koul <vinod.koul@intel.com>
> 
> No, as I wrote before, checking the type isn't enough.
> Assigning a TLV to BYTES type doesn't mean necessarily that it's an
> ASoC EXT control.  You need to check the r/w capabilities as well.

Oops missed that part.

So am making it

if (type == SND_CTL_ELEM_TYPE_BYTES &&
	(snd_ctl_elem_info_is_tlv_readable(info) ||
	snd_ctl_elem_info_is_tlv_writable(info))) {

But this control can be read only or write only. Like a module doesnt allow
read, or some is read only so OR should be good here

Also should it check it is not normal read/write ?

Thanks

-- 
~Vinod

  reply	other threads:[~2016-01-28  6:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28  4:49 [PATCH v2] amixer: skip showing asoc tlv byte controls Vinod Koul
2016-01-28  5:53 ` Takashi Iwai
2016-01-28  6:40   ` Vinod Koul [this message]
2016-01-28  7:04     ` Takashi Iwai

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=20160128064011.GE11130@localhost \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=patches.audio@intel.com \
    --cc=tiwai@suse.de \
    /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.