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: <CAKohponBkA+bg7B4TKaU6WbcVBNDHPe4AWqAEE6JGD7zctoULw@mail.gmail.com> Date: Thu, 6 Dec 2012 08:06:20 +0530 From: Viresh Kumar <viresh.kumar@...aro.org> To: Grant Likely <grant.likely@...retlab.ca> Cc: Lee Jones <lee.jones@...aro.org>, 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 04:12, Grant Likely <grant.likely@...retlab.ca> wrote: > On Sat, 1 Dec 2012 00:33:46 +0530, Viresh Kumar <viresh.kumar@...aro.org> wrote: >> This first tries to match the table my patch added, _BUT_ the string will >> never match as we had "st,stmpe810" in table and "stmpe810" in dev. > > of_driver_match_device() matches against the compatible list in > dev->of_node, not against the device name. So, if the compatible > property has a string that is in the table, then it really should match > against it. Grant, but isn't it true that the final device's name would not be the DT way of names? It would simply be "stmpe810" for us and so if we have multiple instances of stmpe on a board, we need to distinguish them ourselves? One way for that was passing id for these instances, which would finally be used, when we create platform devices for sub-modules of stmpe (gpio, keypad, ts, etc). -- 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