From mboxrd@z Thu Jan  1 00:00:00 1970
From: Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH 1/2] ASoC: Add support for Conexant CX2072X
	CODEC
Date: Wed, 08 May 2019 10:16:06 +0200
Message-ID: <s5hk1f1nyyh.wl-tiwai@suse.de>
References: <20190423141336.12568-1-tiwai@suse.de>
 <20190423141336.12568-2-tiwai@suse.de>
 <20190427175938.GJ14916@sirena.org.uk>
 <s5h36lxpcbd.wl-tiwai@suse.de>
 <20190503064729.GF14916@sirena.org.uk>
 <s5hk1f8m2f1.wl-tiwai@suse.de>
 <20190506042625.GK14916@sirena.org.uk>
 <s5hsgtr6h5y.wl-tiwai@suse.de>
 <20190506140506.GQ14916@sirena.org.uk>
 <s5h4l674n9g.wl-tiwai@suse.de>
 <20190508081006.GZ14916@sirena.org.uk>
Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <alsa-devel-bounces@alsa-project.org>
Received: from mx1.suse.de (mx2.suse.de [195.135.220.15])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by alsa1.perex.cz (Postfix) with ESMTPS id 96AC7F807B5
 for <alsa-devel@alsa-project.org>; Wed,  8 May 2019 10:16:07 +0200 (CEST)
In-Reply-To: <20190508081006.GZ14916@sirena.org.uk>
List-Unsubscribe: <https://mailman.alsa-project.org/mailman/options/alsa-devel>,
 <mailto:alsa-devel-request@alsa-project.org?subject=unsubscribe>
List-Archive: <http://mailman.alsa-project.org/pipermail/alsa-devel/>
List-Post: <mailto:alsa-devel@alsa-project.org>
List-Help: <mailto:alsa-devel-request@alsa-project.org?subject=help>
List-Subscribe: <https://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
 <mailto:alsa-devel-request@alsa-project.org?subject=subscribe>
Errors-To: alsa-devel-bounces@alsa-project.org
Sender: "Alsa-devel" <alsa-devel-bounces@alsa-project.org>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
List-Id: alsa-devel@alsa-project.org

On Wed, 08 May 2019 10:10:06 +0200,
Mark Brown wrote:
> 
> On Mon, May 06, 2019 at 05:26:51PM +0200, Takashi Iwai wrote:
> > Mark Brown wrote:
> 
> > > Like I say if the device is using the fact that the pin is a GPIO
> > > there's quite likely something wrong - that shouldn't be something that
> > > the user of an interrupt should need to see.
> 
> > Yeah, unfortunately we have no reference, so the only chance would be
> > to test with another board that has a different setup.
> 
> The GPIO/IRQ equivalence thing should just be a purely Linux internal
> thing - looking at the driver it appears that there's no need to look at
> the GPIO status, Linux can tell if something is plugged in purely by
> reading the chip registers so the jack status function could directly be
> the interrupt handler.

But it can't see the button status or detect the headset type without
reading the codec's magic registers...  So some help from the codec
side is required, and the irq handler isn't in the codec side because
there is no i2c irq assigned but only ACPI gpio, as far as I checked.


thanks,

Takashi