Re: [PATCH v2] reset: Exclusive resets must be dedicated to a single hardware block

Hi Philipp, On Fri, Oct 5, 2018 at 5:16 PM Philipp Zabel wrote: > On Fri, 2018-10-05 at 14:31 +0200, Geert Uytterhoeven wrote: > [...] > > > > > + eq = (args2.np == args.np && > > > > > + args2.args_count == args.args_count && > > > > > +

Re: [PATCH v2] reset: Exclusive resets must be dedicated to a single hardware block

Hi Philipp, On Fri, Oct 5, 2018 at 5:16 PM Philipp Zabel wrote: > On Fri, 2018-10-05 at 14:31 +0200, Geert Uytterhoeven wrote: > [...] > > > > > + eq = (args2.np == args.np && > > > > > + args2.args_count == args.args_count && > > > > > +

[PATCH v2] reset: Exclusive resets must be dedicated to a single hardware block

In some SoCs multiple hardware blocks may share a reset control. The reset control API for shared resets will only assert such a reset when the drivers for all hardware blocks agree. The exclusive reset control API still allows to assert such a reset, but that impacts all other hardware blocks

[PATCH v2] reset: Exclusive resets must be dedicated to a single hardware block

In some SoCs multiple hardware blocks may share a reset control. The reset control API for shared resets will only assert such a reset when the drivers for all hardware blocks agree. The exclusive reset control API still allows to assert such a reset, but that impacts all other hardware blocks