Am 08.04.2016 um 00:12 schrieb John Youn <john.y...@synopsys.com>:
> On 4/7/2016 1:36 PM, Michael Niewoehner wrote:
>>
>> Am 07.04.2016 um 20:41 schrieb John Youn <john.y...@synopsys.com>:
>>
>>> On 3/31/2016 2:44 PM, Michael Niewoehner wrote:
>&
Am 08.04.2016 um 00:12 schrieb John Youn :
> On 4/7/2016 1:36 PM, Michael Niewoehner wrote:
>>
>> Am 07.04.2016 um 20:41 schrieb John Youn :
>>
>>> On 3/31/2016 2:44 PM, Michael Niewoehner wrote:
>>>> Hi John,
>>>>
>>
Am 07.04.2016 um 20:41 schrieb John Youn <john.y...@synopsys.com>:
> On 3/31/2016 2:44 PM, Michael Niewoehner wrote:
>> Hi John,
>>
>> Am 29.03.2016 um 04:36 schrieb John Youn <johny...@synopsys.com>:
>>
>>> Hi,
>>>
>>>
Am 07.04.2016 um 20:41 schrieb John Youn :
> On 3/31/2016 2:44 PM, Michael Niewoehner wrote:
>> Hi John,
>>
>> Am 29.03.2016 um 04:36 schrieb John Youn :
>>
>>> Hi,
>>>
>>> The following patch series addresses the core reset and for
Hi John,
Am 29.03.2016 um 04:36 schrieb John Youn :
> Hi,
>
> The following patch series addresses the core reset and force mode
> delay problems we have been seeing on dwc2 for some platforms.
>
> I think I have identified the source of the inconsistencies between
>
Hi John,
Am 29.03.2016 um 04:36 schrieb John Youn :
> Hi,
>
> The following patch series addresses the core reset and force mode
> delay problems we have been seeing on dwc2 for some platforms.
>
> I think I have identified the source of the inconsistencies between
> platforms and this series
Hi John,
Am 29.03.2016 um 04:36 schrieb John Youn :
> Hi,
>
> The following patch series addresses the core reset and force mode
> delay problems we have been seeing on dwc2 for some platforms.
>
> I think I have identified the source of the inconsistencies between
>
Hi John,
Am 29.03.2016 um 04:36 schrieb John Youn :
> Hi,
>
> The following patch series addresses the core reset and force mode
> delay problems we have been seeing on dwc2 for some platforms.
>
> I think I have identified the source of the inconsistencies between
> platforms and this series
Hi Douglas,
Hi John,
Am 05.03.2016 um 01:33 schrieb Doug Anderson <diand...@chromium.org>:
> Michael,
>
> On Fri, Mar 4, 2016 at 4:09 PM, Michael Niewoehner <li...@mniewoehner.de>
> wrote:
>>>> From testing and trying to make sense of the documentation
Hi Douglas,
Hi John,
Am 05.03.2016 um 01:33 schrieb Doug Anderson :
> Michael,
>
> On Fri, Mar 4, 2016 at 4:09 PM, Michael Niewoehner
> wrote:
>>>> From testing and trying to make sense of the documentation, it appears
>>>> that a 10 ms delay is needed a
Hi Douglas,
Am 04.03.2016 um 23:54 schrieb Michael Niewoehner <li...@mniewoehner.de>:
> Hi Douglas,
>
> Am 04.03.2016 um 19:23 schrieb Douglas Anderson <diand...@chromium.org>:
>
>> From testing and trying to make sense of the documentation, it appears
>>
Hi Douglas,
Am 04.03.2016 um 23:54 schrieb Michael Niewoehner :
> Hi Douglas,
>
> Am 04.03.2016 um 19:23 schrieb Douglas Anderson :
>
>> From testing and trying to make sense of the documentation, it appears
>> that a 10 ms delay is needed after resetti
ore_reset()").
>
> Signed-off-by: Douglas Anderson <diand...@chromium.org>
Tested-by: Michael Niewoehner <li...@mniewoehner.de>
> ---
> drivers/usb/dwc2/core.c | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/usb/dwc2/core.c b/drivers/usb/dwc2/
lay when forcing
> dr_mode").
>
> Signed-off-by: Douglas Anderson <diand...@chromium.org>
Tested-by: Michael Niewoehner <li...@mniewoehner.de>
> ---
> drivers/usb/dwc2/core.c | 20
> 1 file changed, 20 insertions(+)
>
> diff --git
d-off-by: Douglas Anderson
Tested-by: Michael Niewoehner
> ---
> drivers/usb/dwc2/core.c | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/usb/dwc2/core.c b/drivers/usb/dwc2/core.c
> index 8710b2d3e770..7c4a6cf4c73a 100644
> --- a/drivers/usb/dwc2/co
de").
>
> Signed-off-by: Douglas Anderson
Tested-by: Michael Niewoehner
> ---
> drivers/usb/dwc2/core.c | 20
> 1 file changed, 20 insertions(+)
>
> diff --git a/drivers/usb/dwc2/core.c b/drivers/usb/dwc2/core.c
> index 5e5a0f135b5a..8710b2d3e770
pclk_cpu needs to keep running because it is needed for devices like
the act8865 regulator but with the recent gpio clock handling this is
not always the case anymore. So add it to the list of critical clocks.
Signed-off-by: Michael Niewoehner
Reviewed-by: Heiko Stuebner
---
Changes in v3
pclk_cpu needs to keep running because it is needed for devices like
the act8865 regulator but with the recent gpio clock handling this is
not always the case anymore. So add it to the list of critical clocks.
Signed-off-by: Michael Niewoehner li...@mniewoehner.de
Reviewed-by: Heiko Stuebner he
pclk_cpu needs to keep running because it is needed for devices like
the act8865 regulator but with the recent gpio clock handling this is
not always the case anymore. So add it to the list of critical clocks.
Signed-off-by: Michael Niewoehner
---
Changes in v2:
- adapt commit message
- add
Hi Heiko,
I merged yours and mine :-)
pclk_cpu needs to keep running because it is needed for devices like
the act8865 regulator but with the recent gpio clock handling this is
not always the case anymore. So add it to the list of critical clocks.
Signed-off-by: Michael Niewoehner
---
drivers
gpio clock is getting disabled to save power but pclk_cpu is needed for act8865
regulator
Signed-off-by: Michael Niewoehner
---
drivers/clk/rockchip/clk-rk3188.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clk/rockchip/clk-rk3188.c
b/drivers/clk/rockchip/clk-rk3188.c
index
gpio clock is getting disabled to save power but pclk_cpu is needed for act8865
regulator
Signed-off-by: Michael Niewoehner li...@mniewoehner.de
---
drivers/clk/rockchip/clk-rk3188.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clk/rockchip/clk-rk3188.c
b/drivers/clk/rockchip
Hi Heiko,
I merged yours and mine :-)
pclk_cpu needs to keep running because it is needed for devices like
the act8865 regulator but with the recent gpio clock handling this is
not always the case anymore. So add it to the list of critical clocks.
Signed-off-by: Michael Niewoehner li
pclk_cpu needs to keep running because it is needed for devices like
the act8865 regulator but with the recent gpio clock handling this is
not always the case anymore. So add it to the list of critical clocks.
Signed-off-by: Michael Niewoehner li...@mniewoehner.de
---
Changes in v2:
- adapt
24 matches
Mail list logo