From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: Intel HDA / ca0132: support for Alienware 15 Creative Sound Core3D-EX Date: Wed, 29 Apr 2015 20:42:04 +0200 Message-ID: References: <553AE4CF.3070805@gmx.com> <553E7B34.2080501@gmx.com> <553EB55D.4060701@gmx.com> <55400DF4.2080309@gmx.com> <5540FBFF.6020904@gmx.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id A241D2605FC for ; Wed, 29 Apr 2015 20:42:04 +0200 (CEST) In-Reply-To: <5540FBFF.6020904@gmx.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Gabriele Martino Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org At Wed, 29 Apr 2015 17:42:55 +0200, Gabriele Martino wrote: > > On 29/04/2015 15:38, Takashi Iwai wrote: > > At Wed, 29 Apr 2015 00:47:16 +0200, > > Gabriele Martino wrote: > >> Thank you for your explanation. > >> I managed to fix the pin address, but as I told before the jack > >> detection is totally messed up. > >> "hdajacksensetest" fails with: > >> Ioctl call failed with error 16 > > The error message looks irrelevant with the patch itself. > > Did you build with proper kernel configs? > > CONFIG_SND_HDA_HWDEP=y > > CONFIG_SND_HDA_RECONFIG=y > > CONFIG_SND_HDA_PATCH_LOADER=y > It should be ok: > > $ grep CONFIG_SND_HDA_ /usr/src/linux/.config | grep -v '^#' > CONFIG_SND_HDA_INTEL=m > CONFIG_SND_HDA_DSP_LOADER=y > CONFIG_SND_HDA_PREALLOC_SIZE=2048 > CONFIG_SND_HDA_HWDEP=y > CONFIG_SND_HDA_RECONFIG=y > CONFIG_SND_HDA_INPUT_JACK=y > CONFIG_SND_HDA_PATCH_LOADER=y > CONFIG_SND_HDA_CODEC_HDMI=m > CONFIG_SND_HDA_I915=y > CONFIG_SND_HDA_CODEC_CA0132=m > CONFIG_SND_HDA_CODEC_CA0132_DSP=y > CONFIG_SND_HDA_GENERIC=m > CONFIG_SND_HDA_POWER_SAVE_DEFAULT=60 OK, then it's something else. Errno 16 is EBUSY, so something else must be accessing the same device (e.g. hwdep) and blocking the operation. Are you sure that you never see this error when a kernel is without the patch? Takashi