lists.openwall.net | 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
| ||
|
Date: Tue, 27 Nov 2012 08:10:28 +0530 From: Viresh Kumar <viresh.kumar@...aro.org> To: Grant Likely <grant.likely@...retlab.ca> Cc: lee.jones@...aro.org, sameo@...ux.intel.com, devicetree-discuss@...ts.ozlabs.org, spear-devel@...t.st.com, linux-kernel@...r.kernel.org Subject: Re: [PATCH V3 3/3] mfd: stmpe: Update DT support in stmpe driver On 27 November 2012 00:10, Grant Likely <grant.likely@...retlab.ca> wrote: > Ah, so it is configuring the way the device emits interrupts; not how > the interrupt controller processes them. Fair enough. Finally i am able to convince somebody that stmpe is different :) > It would actually be good to ask the interrupt controller driver what > kind of interrupt signal it expects for a given interrupt line. That > should also solve the problem and I think it would be more useful to > other devices. Can you investigate whether or not > irqd_get_trigger_type() returns the information you need? That's a pretty cool function to use. :) Will check it out :) -- viresh -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists