Re: [PATCH 1/2] clk: at91: Added more information logging.

2018-04-08 Thread Alan Stern
On Sun, 8 Apr 2018, Marcin wrote: > I noticed that when debugging some USB clocking issue that there weren't > many ways to tell what the state of the USB clocking system was. This > adds a few logging statements to see what the relevant code is trying to > do. > > Signed-off-by: Marcin

Re: [PATCH 1/2] clk: at91: Added more information logging.

2018-04-08 Thread Alan Stern
On Sun, 8 Apr 2018, Marcin wrote: > I noticed that when debugging some USB clocking issue that there weren't > many ways to tell what the state of the USB clocking system was. This > adds a few logging statements to see what the relevant code is trying to > do. > > Signed-off-by: Marcin

Re: [PATCH 1/2] clk: at91: Added more information logging.

2018-04-08 Thread Marcin Ziemianowicz
On Sun, Apr 08, 2018 at 11:54:49AM +0200, Greg Kroah-Hartman wrote: > On Sun, Apr 08, 2018 at 05:43:30AM -0400, Marcin wrote: > > I noticed that when debugging some USB clocking issue that there weren't > > many ways to tell what the state of the USB clocking system was. This > > adds a few

Re: [PATCH 1/2] clk: at91: Added more information logging.

2018-04-08 Thread Marcin Ziemianowicz
On Sun, Apr 08, 2018 at 11:54:49AM +0200, Greg Kroah-Hartman wrote: > On Sun, Apr 08, 2018 at 05:43:30AM -0400, Marcin wrote: > > I noticed that when debugging some USB clocking issue that there weren't > > many ways to tell what the state of the USB clocking system was. This > > adds a few

Re: [PATCH 1/2] clk: at91: Added more information logging.

2018-04-08 Thread Greg Kroah-Hartman
On Sun, Apr 08, 2018 at 05:43:30AM -0400, Marcin wrote: > I noticed that when debugging some USB clocking issue that there weren't > many ways to tell what the state of the USB clocking system was. This > adds a few logging statements to see what the relevant code is trying to > do. > >

Re: [PATCH 1/2] clk: at91: Added more information logging.

2018-04-08 Thread Greg Kroah-Hartman
On Sun, Apr 08, 2018 at 05:43:30AM -0400, Marcin wrote: > I noticed that when debugging some USB clocking issue that there weren't > many ways to tell what the state of the USB clocking system was. This > adds a few logging statements to see what the relevant code is trying to > do. > >

[PATCH 1/2] clk: at91: Added more information logging.

2018-04-08 Thread Marcin
I noticed that when debugging some USB clocking issue that there weren't many ways to tell what the state of the USB clocking system was. This adds a few logging statements to see what the relevant code is trying to do. Signed-off-by: Marcin Ziemianowicz ---

[PATCH 1/2] clk: at91: Added more information logging.

2018-04-08 Thread Marcin
I noticed that when debugging some USB clocking issue that there weren't many ways to tell what the state of the USB clocking system was. This adds a few logging statements to see what the relevant code is trying to do. Signed-off-by: Marcin Ziemianowicz --- drivers/clk/at91/clk-pll.c | 6