lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 6 Dec 2017 11:15:12 -0600
From:   "Andrew F. Davis" <>
To:     Mark Brown <>
CC:     Liam Girdwood <>,
        Rob Herring <>,
        Mark Rutland <>,
        BenoƮt Cousson <>,
        Tony Lindgren <>,
        <>, <>,
Subject: Re: [PATCH v2 16/19] ASoC: tlv320aic31xx: Add short circuit detection

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.

Powered by blists - more mailing lists