Hello, I am working with a hardware design utilizing SX1506 GPIO expander (actually it uses 1503, but they seem to be the same from SW's point of view) and following are the pathches I had to make in order to be able to succesfully use part's driver from upstream kernel. I am pretty certain I did not do any of the DT bindings in a proper way, so I am more than happy to change all of that, or, due to the fact I don't use any of those bindings in my usecase, drop them alltogether. Thank you, Andrey Smirnov Andrey Smirnov (13): gpio-sx150x: Remove 'gpio_base' from pdata gpio-sx150x: Remove 'irq_summary' parameter gpio-sx150x: Remove 'irq_base' parameter gpio-sx150x: Replace 'io_polarity' with DT binding bindings: gpio-sx150x: Document "semtech,io-polarity" binding gpio-sx150x: Replace "io_pull*_ena" with DT bindings bindings: gpio-sx150x: Document "semtech,io-pull*" bindings gpio-sx150x: Replace 'reset_during_probe" with DT binding bindings: gpio-sx150x: Document "semtech,reset-during-probe" bindings gpio-sx150x: Replace 'oscio_is_gpio' with DT binding bindings: gpio-sx150x: Document "semtech,oscio-is-gpo" binding gpio-sx150x: Remove struct sx150x_platform_data gpio-sx150x: Pass device type in DT match table .../devicetree/bindings/gpio/gpio-sx150x.txt | 29 ++++ drivers/gpio/gpio-sx150x.c | 184 +++++++++------------ 2 files changed, 105 insertions(+), 108 deletions(-) -- 2.5.5 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
