On Thu, 30 Jun 2016 23:16:35 +0200 Maxime Ripard <maxime.ripard@xxxxxxxxxxxxxxxxxx> wrote: > > - in case a driver requests a reset, this last one should exist. > > But, this reset may point to a void one (reg = null) when the real > > reset has been moved to the prepare/unprepare of the associated clock. > > And what if this driver wants to be reset, by calling > reset_control_reset? You realize you're going against the semantics of > the reset and clock APIs, and what the hardware expose here right? If a driver really wants a reset, the reset stuff is not included in the clock prepare. -- Ken ar c'hentañ | ** Breizh ha Linux atav! ** Jef | http://moinejf.free.fr/ -- 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
