From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752679AbdLFRPb (ORCPT ); Wed, 6 Dec 2017 12:15:31 -0500 Received: from lelnx193.ext.ti.com ([198.47.27.77]:15480 "EHLO lelnx193.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752387AbdLFRPZ (ORCPT ); Wed, 6 Dec 2017 12:15:25 -0500 Subject: Re: [PATCH v2 16/19] ASoC: tlv320aic31xx: Add short circuit detection support To: Mark Brown CC: Liam Girdwood , Rob Herring , Mark Rutland , =?UTF-8?Q?Beno=c3=aet_Cousson?= , Tony Lindgren , , , References: <20171129213300.20021-1-afd@ti.com> <20171129213300.20021-17-afd@ti.com> <20171201133930.xzfjjj6wzkbtk6c4@sirena.org.uk> <4d956cbc-829c-0d81-2980-aa2a79f36660@ti.com> <20171201155725.lrl35nig53fnwkac@sirena.org.uk> From: "Andrew F. Davis" Message-ID: <73ee66e9-81c3-2bfe-8808-2c3e90f5bcba@ti.com> Date: Wed, 6 Dec 2017 11:15:12 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171201155725.lrl35nig53fnwkac@sirena.org.uk> Content-Type: text/plain; charset="windows-1252" Content-Language: en-US Content-Transfer-Encoding: 7bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/01/2017 09:57 AM, Mark Brown wrote: > On Fri, Dec 01, 2017 at 09:32:12AM -0600, Andrew F. Davis wrote: >> On 12/01/2017 07:39 AM, Mark Brown wrote: > >>> Is the interrupt only available on GPIO1? > >> Some devices can route this to GPIO2 IIRC. > >> I'm not sure how that would be supported, I think we would need to add >> interrupt names to DT so users could specify which gpio they wired their >> IRQ lines to. > >> interrupt = <&host 23>; >> interrupt-name = "gpio2"; > >> or similar? > > You could also use pinctrl an require the user to mux the interrupt in > whatever fashion makes sense for their device. > If done at that layer then no change is needed in the driver right? We just request and use the IRQ passed to us from i2c data.