[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <279c42970790787e928ed017149e300835085235.camel@kernel.crashing.org>
Date: Tue, 30 Nov 2021 10:45:44 +1100
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: Neal Liu <neal_liu@...eedtech.com>,
Felipe Balbi <balbi@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Joel Stanley <joel@....id.au>,
Andrew Jeffery <andrew@...id.au>,
Cai Huoqing <caihuoqing@...du.com>,
Tao Ren <rentao.bupt@...il.com>,
Julia Lawall <julia.lawall@...ia.fr>,
kernel test robot <lkp@...el.com>,
Sasha Levin <sashal@...nel.org>, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-aspeed@...ts.ozlabs.org
Cc: BMC-SW@...eedtech.com
Subject: Re: [PATCH 2/3] usb: aspeed-vhub: support remote wakeup feature
On Fri, 2021-11-26 at 19:09 +0800, Neal Liu wrote:
> Remote wakeup signaling will be automatically issued
> whenever any write commands has been received in suspend
> state.
> --- a/drivers/usb/gadget/udc/aspeed-vhub/core.c
> +++ b/drivers/usb/gadget/udc/aspeed-vhub/core.c
> @@ -240,6 +240,9 @@ void ast_vhub_init_hw(struct ast_vhub *vhub)
> if (vhub->force_usb1)
> ctrl |= VHUB_CTRL_FULL_SPEED_ONLY;
>
> + /* Enable auto remote wakeup */
> + ctrl |= VHUB_CTRL_AUTO_REMOTE_WAKEUP;
> +
> ctrl |= VHUB_CTRL_UPSTREAM_CONNECT;
> writel(ctrl, vhub->regs + AST_VHUB_CTRL);
Should this be controlled by d->wakeup_en ? IE, we have a feature for
the host to enable/disable remote wakeup, should we honor it ?
> + } else if (wValue == USB_DEVICE_TEST_MODE) {
> + val = readl(d->vhub->regs + AST_VHUB_CTRL);
> + val &= ~GENMASK(10, 8);
> + val |= VHUB_CTRL_SET_TEST_MODE((wIndex >> 8) & 0x7);
> + writel(val, d->vhub->regs + AST_VHUB_CTRL);
This is unrelated to remote wakeup is it ? In which case it should
probably be a separate patch.
Cheers,
Ben.
Powered by blists - more mailing lists