[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAODwPW8r0cq2aozVjY9o9wOwqa4Nn1Oom9+Td8e-H0FoDf-LfQ@mail.gmail.com>
Date: Mon, 17 Nov 2014 13:21:25 -0800
From: Julius Werner <jwerner@...omium.org>
To: Kever Yang <kever.yang@...k-chips.com>
Cc: Paul Zimmerman <paulz@...opsys.com>, Felipe Balbi <balbi@...com>,
Dinh Nguyen <dinguyen@...nsource.altera.com>,
Romain Perier <romain.perier@...il.com>,
Heiko Stuebner <heiko@...ech.de>,
Douglas Anderson <dianders@...omium.org>,
Sonny Rao <sonnyrao@...omium.org>,
addy ke <addy.ke@...k-chips.com>,
Eddie Cai <cf@...k-chips.com>, wulf <wulf@...k-chips.com>,
Tao Huang <huangtao@...k-chips.com>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
Roy Li <roy.li@...k-chips.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] usb: dwc2: resume root hub when device detect with
suspend state
On Mon, Nov 17, 2014 at 5:14 AM, Kever Yang <kever.yang@...k-chips.com> wrote:
> After we implement the bus_suspend/resume, auto suspend id enabled.
> The root hub will be auto suspend if there is no device connected,
> we need to resume the root hub when a device connect detect.
>
> This patch tested on rk3288.
>
> Signed-off-by: Roy Li <roy.li@...k-chips.com>
> Signed-off-by: Kever Yang <kever.yang@...k-chips.com>
> ---
>
> drivers/usb/dwc2/hcd_intr.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/usb/dwc2/hcd_intr.c b/drivers/usb/dwc2/hcd_intr.c
> index 551ba87..c8299fd 100644
> --- a/drivers/usb/dwc2/hcd_intr.c
> +++ b/drivers/usb/dwc2/hcd_intr.c
> @@ -355,6 +355,13 @@ static void dwc2_port_intr(struct dwc2_hsotg *hsotg)
> hprt0_modify |= HPRT0_CONNDET;
>
> /*
> + * Check if root hub is in suspend state
> + * if root hub in suspend, resume it.
> + */
> + if ((bus->root_hub) && (hcd->state == HC_STATE_SUSPENDED))
What is bus->root_hub checking for? Is there any chance that this
could be NULL here?
> + usb_hcd_resume_root_hub(hcd);
> +
> + /*
> * The Hub driver asserts a reset when it sees port connect
> * status change flag
> */
> --
> 1.9.1
Seems sensible in general. Does this actually fix the problem Doug was
reporting?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists