From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C27F1C43334 for ; Mon, 27 Jun 2022 01:33:47 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229732AbiF0Bdr (ORCPT ); Sun, 26 Jun 2022 21:33:47 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60220 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229603AbiF0Bdq (ORCPT ); Sun, 26 Jun 2022 21:33:46 -0400 Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 716EE2673; Sun, 26 Jun 2022 18:33:45 -0700 (PDT) Received: from ip6-localhost (localhost.localdomain [127.0.0.1]) by gate.crashing.org (8.14.1/8.14.1) with ESMTP id 25R1UGbi027657; Sun, 26 Jun 2022 20:30:18 -0500 Message-ID: Subject: Re: [PATCH] usb: gadget: aspeed_udc: fix handling of tx_len == 0 From: Benjamin Herrenschmidt To: Neal Liu , Dan Carpenter Cc: "gregkh@linuxfoundation.org" , "linux-usb@vger.kernel.org" , "kernel-janitors@vger.kernel.org" , "linux-aspeed@lists.ozlabs.org" , "balbi@kernel.org" Date: Mon, 27 Jun 2022 11:30:15 +1000 In-Reply-To: References: <20220623064320.GN16517@kadam> <20220624063457.GG11460@kadam> <46f88070d8f6f47f55310e964a4576cadbc810f4.camel@kernel.crashing.org> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5-0ubuntu1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: kernel-janitors@vger.kernel.org On Fri, 2022-06-24 at 07:46 +0000, Neal Liu wrote: > > > Hi Ben, This UDC is the independent IP. The ast2600 board can run > aspeed-vhub & aspeed_udc simultaneously with different USB port. > I think it's no need to restruct the code in vhub. But is it a copy of the same base IP block ? IE, is the fundamental HW interface of the independent UDC operating the same way with the same register layout as one of the ports of the vHUB ? I don't like having multiple drivers for the same hardware... if it's different enough, then let's keep it separate, but if not, we should definitely split the udc from the existing vhub code so that the same driver can operate standalone or beneath a vhub. Cheers, Ben.