[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <84b2d2c6b530d0a3a9b86b0ffcbfa70935bdb0a9.camel@kernel.crashing.org>
Date: Tue, 30 Nov 2021 10:40:59 +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 1/3] usb: aspeed-vhub: add qualifier descriptor
On Fri, 2021-11-26 at 19:09 +0800, Neal Liu wrote:
>
> @@ -417,10 +435,9 @@ enum std_req_rc ast_vhub_std_hub_request(struct ast_vhub_ep *ep,
>
> /* GET/SET_CONFIGURATION */
> case DeviceRequest | USB_REQ_GET_CONFIGURATION:
> - return ast_vhub_simple_reply(ep, 1);
> + return ast_vhub_simple_reply(ep, vhub->current_config);
> case DeviceOutRequest | USB_REQ_SET_CONFIGURATION:
> - if (wValue != 1)
> - return std_req_stall;
> + vhub->current_config = wValue;
> return std_req_complete;
This is odd.. why should we support arbitrary SET_CONFIGURATION for
configs we don't support ?
Otherwise looks good.
Cheers,
Ben.
Powered by blists - more mailing lists