On Tue, Jan 20, 2015 at 08:36:03AM -0600, Felipe Balbi wrote:
> Hi,
>
> On Tue, Jan 20, 2015 at 08:13:57AM +, Paul Walmsley wrote:
> > On Tue, 20 Jan 2015, Paul Walmsley wrote:
> >
> > > On Fri, 5 Dec 2014, Felipe Balbi wrote:
> > >
> > > > By exposing the details of hwmod structures
> > > >
Hi,
On Tue, Jan 20, 2015 at 08:13:57AM +, Paul Walmsley wrote:
> On Tue, 20 Jan 2015, Paul Walmsley wrote:
>
> > On Fri, 5 Dec 2014, Felipe Balbi wrote:
> >
> > > By exposing the details of hwmod structures
> > > to debugfs we can much more easily verify
> > > that changes to hwmod data is c
On Tue, 20 Jan 2015, Paul Walmsley wrote:
> On Fri, 5 Dec 2014, Felipe Balbi wrote:
>
> > By exposing the details of hwmod structures
> > to debugfs we can much more easily verify
> > that changes to hwmod data is correct and won't
> > cause regressions.
> >
> > The idea is that this can be used
On Fri, 5 Dec 2014, Felipe Balbi wrote:
> By exposing the details of hwmod structures
> to debugfs we can much more easily verify
> that changes to hwmod data is correct and won't
> cause regressions.
>
> The idea is that this can be used to check the
> state of one hwmod, verify hwmod sysc field
By exposing the details of hwmod structures
to debugfs we can much more easily verify
that changes to hwmod data is correct and won't
cause regressions.
The idea is that this can be used to check the
state of one hwmod, verify hwmod sysc fields, etc.
For example, this will be used to move some of