Re: [PATCH] clk: pxa: pxa3xx: fix CKEN register access

2015-08-04 Thread Robert Jarzmik
Stephen Boyd writes: > On 08/04/2015 11:33 AM, Robert Jarzmik wrote: >> Stephen Boyd writes: >> >>> On 08/03/2015 11:22 PM, Robert Jarzmik wrote: Stephen Boyd writes: > On 08/03/2015 12:58 PM, Robert Jarzmik wrote: >> Clocks 0 to 31 are on CKENA, and not CKENB. The clock regis

Re: [PATCH] clk: pxa: pxa3xx: fix CKEN register access

2015-08-04 Thread Stephen Boyd
On 08/04/2015 11:33 AM, Robert Jarzmik wrote: Stephen Boyd writes: On 08/03/2015 11:22 PM, Robert Jarzmik wrote: Stephen Boyd writes: On 08/03/2015 12:58 PM, Robert Jarzmik wrote: Clocks 0 to 31 are on CKENA, and not CKENB. The clock register names were inadequately inverted. As a consequ

Re: [PATCH] clk: pxa: pxa3xx: fix CKEN register access

2015-08-04 Thread Robert Jarzmik
Stephen Boyd writes: > On 08/03/2015 11:22 PM, Robert Jarzmik wrote: >> Stephen Boyd writes: >> >>> On 08/03/2015 12:58 PM, Robert Jarzmik wrote: Clocks 0 to 31 are on CKENA, and not CKENB. The clock register names were inadequately inverted. As a consequence, all clock operations were

Re: [PATCH] clk: pxa: pxa3xx: fix CKEN register access

2015-08-04 Thread Stephen Boyd
On 08/03/2015 11:22 PM, Robert Jarzmik wrote: Stephen Boyd writes: On 08/03/2015 12:58 PM, Robert Jarzmik wrote: Clocks 0 to 31 are on CKENA, and not CKENB. The clock register names were inadequately inverted. As a consequence, all clock operations were happening on CKENB, because almost all

Re: [PATCH] clk: pxa: pxa3xx: fix CKEN register access

2015-08-03 Thread Robert Jarzmik
Stephen Boyd writes: > On 08/03/2015 12:58 PM, Robert Jarzmik wrote: >> Clocks 0 to 31 are on CKENA, and not CKENB. The clock register names >> were inadequately inverted. As a consequence, all clock operations were >> happening on CKENB, because almost all but 2 clocks are on CKENA. >> >> As the

Re: [PATCH] clk: pxa: pxa3xx: fix CKEN register access

2015-08-03 Thread Stephen Boyd
On 08/03/2015 12:58 PM, Robert Jarzmik wrote: Clocks 0 to 31 are on CKENA, and not CKENB. The clock register names were inadequately inverted. As a consequence, all clock operations were happening on CKENB, because almost all but 2 clocks are on CKENA. As the clocks were activated by the bootloa

[PATCH] clk: pxa: pxa3xx: fix CKEN register access

2015-08-03 Thread Robert Jarzmik
Clocks 0 to 31 are on CKENA, and not CKENB. The clock register names were inadequately inverted. As a consequence, all clock operations were happening on CKENB, because almost all but 2 clocks are on CKENA. As the clocks were activated by the bootloader in the former tests, it escaped the testing