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
| ||
|
Message-ID: <CAKohponrZ8a+=ozXox60nRVBO174Nr=GoSjKkkz7KjLCxd5BhQ@mail.gmail.com> Date: Thu, 6 Dec 2012 16:49:47 +0530 From: Viresh Kumar <viresh.kumar@...aro.org> To: Lee Jones <lee.jones@...aro.org> Cc: Grant Likely <grant.likely@...retlab.ca>, Samuel Ortiz <sameo@...ux.intel.com>, rabin.vincent@...ricsson.com, shiraz.hashim@...com, devicetree-discuss@...ts.ozlabs.org, linux-kernel@...r.kernel.org, spear-devel@...t.st.com, linus.walleij@...aro.org, Vipul Kumar Samar <vipulkumar.samar@...com> Subject: Re: [PATCH V5 2/2] mfd: stmpe: Update DT support in stmpe driver On 6 December 2012 16:42, Lee Jones <lee.jones@...aro.org> wrote: > I thought we'd be over this? The 'ID' will be represented by the > address of the chip i.e. stmpe1601@40, where '40' will be > distinguishing factor? I haven't tested it but i thought we are getting i2c device name from modalias() fn running on "st,stmpe1601" and so would give us "stmpe1601". Now, i went back to your earlier mail and checked device name: stmpe-i2c 0-0040: stmpe1601 detected, chip id: 0x212 It came from DT :) So, probably no more issues of id's. Will resend my patch, after getting rid of tables. -- 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