All of lore.kernel.org
 help / color / mirror / Atom feed
From: Angelo Dureghello <angelo70@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Wolfson codec, problem on mixer levels on kernel 3.17.0
Date: Mon, 20 Oct 2014 09:19:44 +0200	[thread overview]
Message-ID: <5444B790.8000203@gmail.com> (raw)

Hi,

moving from kernel 3.5.1 to 3.17, amixer cannot read certain mixer 
controls,
giving Input/output error:

[root@test ~]# amixer cget numid=12
numid=12,iface=MIXER,name='Capture Volume'
   ; type=INTEGER,access=rw---R--,values=2,min=0,max=255,step=0
amixer: Control default element read error: Input/output error

So i had to disable those controls in the codec code:

     ...

     //SOC_DOUBLE_R_TLV("Capture Volume", WM8758_LEFT_ADC_DIGITAL_VOL,
     //    WM8758_RIGHT_ADC_DIGITAL_VOL, 0, 255, 0, adc_tlv),
     ...
     //SOC_SINGLE("DAC Playback Limiter Switch", WM8758_DAC_LIMITER_1, 
8, 1, 0),
     //SOC_SINGLE("DAC Playback Limiter Decay", WM8758_DAC_LIMITER_1, 4, 
10, 0),
     //SOC_SINGLE("DAC Playback Limiter Attack", WM8758_DAC_LIMITER_1, 
0, 11, 0),
     ...
     //SOC_ENUM("EQ4 Bandwith", eq4_bw),
     //SOC_ENUM("EQ4 Cutoff", eq4_cutoff),
     //SOC_SINGLE_TLV("EQ4 Volume", WM8758_EQ4_PEAK_3, 0, 24, 1, eq_tlv),
     ...

Is it possible sonething is changed in these macroes, so that the amixer 
cannot
access the controls anymore ?

Every help is appreciated,
many thanks
angelo

             reply	other threads:[~2014-10-20  7:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-20  7:19 Angelo Dureghello [this message]
2014-10-20  8:08 ` Wolfson codec, problem on mixer levels on kernel 3.17.0 Lars-Peter Clausen

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=5444B790.8000203@gmail.com \
    --to=angelo70@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    /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.