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 27536C433F5 for ; Mon, 28 Feb 2022 18:39:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240691AbiB1SkG (ORCPT ); Mon, 28 Feb 2022 13:40:06 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38018 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240863AbiB1Sjv (ORCPT ); Mon, 28 Feb 2022 13:39:51 -0500 Received: from mail-pl1-x634.google.com (mail-pl1-x634.google.com [IPv6:2607:f8b0:4864:20::634]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BB0484477C for ; Mon, 28 Feb 2022 10:28:56 -0800 (PST) Received: by mail-pl1-x634.google.com with SMTP id q11so11467828pln.11 for ; Mon, 28 Feb 2022 10:28:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=953U8rJ4XL9BO0MAZAoSvNfxJjSMk/eYFo8dV60tgFc=; b=FpK1ngedQX3i3ivR3W3a6s9CDUpEcLJ7+K72A8HWuIj+TG9fFxdNTS8IxACdRptz5O VJNsv0VTwQYiTNicWanwklaKPytRcWWcHmq0OX9OJRvN6X7P2PKdM58VR1MdzviHqS6h NnRbxHH8agrt2Ew2iEAOGcbFr3lrxgtJSG0lw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=953U8rJ4XL9BO0MAZAoSvNfxJjSMk/eYFo8dV60tgFc=; b=nLz+wnMLPhKcJ14zlUsVOBQuGkqr2mxwrPjkhe0ioeE5Zt2n/Y87XxZJ3M3CXtMxwx HzXKLJUF1YEz2ADW+jniBjvaykE+0PmXRdxBJMckVkuZAS44zbayqYci0GjdectYAuh9 BGI+zajQziN3dElughiiVixNHcpG8meWNbPei0AOaH1rp+ijEfT9QXv4FVDDyB+mgxC3 z5OKwpqLaE+WeW3OyNjigFkkBTkyGdpcmxd7CTx3Q7bQhijm7RJ45Qp+ckKQbrzqzdju F1sopL707iccAexkn4MOaFnVEf9HvuRpB8H9MSQ3VZSCB/q22jNHl6PnIjenTOhGvT7R Tm6A== X-Gm-Message-State: AOAM532bJguoMirIxyQu3ewSR0eb/kzabpX4rsBObrfiiHxn7f5ZbaFF GKjvbMT4klsnRkBWbNSGuHdBdQ== X-Google-Smtp-Source: ABdhPJwK4X9UEdRlczlObVA8zipBl9vNEDhwutWp0ODiei04VVcvgZUDYK9KSHSJekx+YOkQqo2U/g== X-Received: by 2002:a17:903:2041:b0:14f:b0a6:18f5 with SMTP id q1-20020a170903204100b0014fb0a618f5mr22231706pla.50.1646072936309; Mon, 28 Feb 2022 10:28:56 -0800 (PST) Received: from localhost ([2620:15c:202:201:f16d:303:27ee:ee6a]) by smtp.gmail.com with UTF8SMTPSA id a8-20020a17090a740800b001bc691c79fcsm64964pjg.49.2022.02.28.10.28.54 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 28 Feb 2022 10:28:55 -0800 (PST) Date: Mon, 28 Feb 2022 10:28:53 -0800 From: "mka@chromium.org" To: "Linyu Yuan (QUIC)" Cc: "gregkh@linuxfoundation.org" , "Tao Wang (Consultant) (QUIC)" , "balbi@kernel.org" , "devicetree@vger.kernel.org" , "dianders@chromium.org" , "frowand.list@gmail.com" , "hadess@hadess.net" , "krzk@kernel.org" , "linux-kernel@vger.kernel.org" , "linux-usb@vger.kernel.org" , "mathias.nyman@intel.com" , "michal.simek@xilinx.com" , "peter.chen@kernel.org" , "ravisadineni@chromium.org" , "robh+dt@kernel.org" , "rogerq@kernel.org" , "stern@rowland.harvard.edu" , "swboyd@chromium.org" Subject: Re: =?utf-8?B?5Zue5aSNOiDlm57lpI0=?= =?utf-8?Q?=3A?= Re: [PATCH v20 3/5] usb: misc: Add onboard_usb_hub driver Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org On Mon, Feb 28, 2022 at 03:08:34AM +0000, Linyu Yuan (QUIC) wrote: > > From: gregkh@linuxfoundation.org > > Sent: Wednesday, February 23, 2022 3:56 PM > > To: Tao Wang (Consultant) (QUIC) > > Cc: mka@chromium.org; balbi@kernel.org; devicetree@vger.kernel.org; > > dianders@chromium.org; frowand.list@gmail.com; hadess@hadess.net; > > krzk@kernel.org; linux-kernel@vger.kernel.org; linux-usb@vger.kernel.org; > > mathias.nyman@intel.com; michal.simek@xilinx.com; > > peter.chen@kernel.org; ravisadineni@chromium.org; robh+dt@kernel.org; > > rogerq@kernel.org; stern@rowland.harvard.edu; swboyd@chromium.org; > > Linyu Yuan (QUIC) > > Subject: Re: 回复: 回复: Re: [PATCH v20 3/5] usb: misc: Add > > onboard_usb_hub driver > > > > On Wed, Feb 23, 2022 at 07:40:31AM +0000, Tao Wang (Consultant) (QUIC) > > wrote: > > > Ok, thanks your reply. > > > > > > Here is my question, we must modify the driver "onboard_usb_hub.c" if > > we want to use it. But it's hard to complete because it's an opensource code. > > > > I do not understand. We do not deal with code that is not in the kernel > > source tree, as we have no idea what is out there. Please just submit > > your changes to be merged into the tree and all will be fine. > > Hi Greg and mka, > > Let's make it clear that we are talking about once this driver is approved into usb tree, > If we use different USB HUB which have VID/PID not defined in this driver, > We need to update this driver. > > But if we defined VID/PID in device tree(for a specific board, manufacture should know VID/PID from HUB it used), > dynamic parsed by the driver, then we don't need to change this driver (increase VID/PID table). As per my earlier reply, the kernel/USB core uses the VID:PID reported by the USB device, the compatible string in the device tree is purely informational. That's not something that could be changed by this driver. And even if the VID:PID from the device tree was used: how is the kernel supposed to know that the onboard_hub driver should be probed for a given VID:PID from the device tree, without listing the VID:PID (or compatible string) in the driver (which is what you seem to seek to avoid)?