* Marcin Niestroj <m.niestroj@xxxxxxxxxxxxxxxx> [160426 00:40]: > In below code we check reg resource size in order to know if we > should update RTC_PMIC or it is pinctrl responsibility. It's a little > hack, but we make sure, that every device with not modified device-tree > will work as previously. If we want to add support for ext_wakeup, we > just change reg resouce size in device-tree in order to not overlap > requested memory regions in rtc-omap and pinctrl. > > I used am335x-chilisom instead of dra7 and updated > pinctrl-single,funcion-mask so the EXT_WAKEUP_STATUS is always cleared > after boot. > > So the question now is: is this acceptable? Do we want to continue with > this approach? Well the concern I have here is that we not use pinctrl-single as a separate driver if any of the registers are shared with the RTC driver. If the registers are shared, the pinctrl functionality should be implemented in the RTC driver. The pinctrl driver can also implement a chained IRQ later on for consumer device drivers to use with the wakeirq API. Maybe eventually we'll have real chained interrupt for the RTC to use from Linux side of the C-M3 driver. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
