Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp1756258pxj; Wed, 19 May 2021 13:11:15 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzsZEtXquaSLQ5Gx2TCzUXh4BAeot6ncS5aO68RcBGtYVFM852C2H4dAdL8srtRp88fmJZm X-Received: by 2002:a17:906:f894:: with SMTP id lg20mr870083ejb.355.1621455075538; Wed, 19 May 2021 13:11:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1621455075; cv=none; d=google.com; s=arc-20160816; b=oYW7aEu2oaCoTbcrInrc8CmED/WST8pESj1//y3m9ZPC+kItZkVQSltoWqx9+g5a5t W2h3HBj+nOwjb/JavrCpzg4wiGU4/6H+hexDakrdNjfy9lsbfRLZOSNGHlc5jy27kZDO gj5oF80nf3N1+Cgzdgh84qQ+tVW4oSbEbZmF6tUYf4IIVBGd8rwkACqc0CXZxCqaZjO3 rg58S1q+Rz0db/KuVP3uMvrcJ1m94L6aTfzoB3JpK92dQRovNtk47B6L369ExhW98NnR 7T7N6HMOF9yCqF6lEPEKYHiwR+yvlQB/d8U9tj/Gy+Q4z7Az4d90y4FaN/8GNZmgme7U uPnQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=HF4r5NkgEKo0vT4j5HIC0UlkT3D70W1m5bf4plMPO7U=; b=cINR7Mz0FCfP9pbRzL4L9NurxmE8TGX6pHGiFE4YjxT3ByFJFZDzs/kzb3RDXe9Dmb tegoB05i5zmH/iUwkuP/G6Pown3zQ3jRs2eOKeyVDUdto95eMxLG1xcYM6RXb+CZEBs2 Lmq59bL6SzNyQqNEpTpUYEsuBdyQXVpcYXbSOdbpUQuA7tUNN+WsT87Vow5L5QcskQrQ 0QFM2rVuGvfVTrAGGAGHxkbnoj3CdgxcVhPg1WUZN3cd7jo8YwAHlNi44Uv+NHW0z3uc wiOtNc2zMPKuO/5QnF7B1U9/bXHxiskb5EUSB+F0fw5kgcEBlh2XmeTCarEDL4PFhpTq Nrdg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id x10si554975eji.476.2021.05.19.13.10.51; Wed, 19 May 2021 13:11:15 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1354719AbhESOqI (ORCPT + 99 others); Wed, 19 May 2021 10:46:08 -0400 Received: from netrider.rowland.org ([192.131.102.5]:49217 "HELO netrider.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1354360AbhESOpR (ORCPT ); Wed, 19 May 2021 10:45:17 -0400 Received: (qmail 1166961 invoked by uid 1000); 19 May 2021 10:43:56 -0400 Date: Wed, 19 May 2021 10:43:56 -0400 From: Alan Stern To: Matthias Kaehlcke Cc: Greg Kroah-Hartman , Rob Herring , Frank Rowand , Michal Simek , devicetree@vger.kernel.org, Douglas Anderson , linux-usb@vger.kernel.org, Peter Chen , linux-kernel@vger.kernel.org, Stephen Boyd , Ravi Chandra Sadineni , Krzysztof Kozlowski , Bastien Nocera , Al Cooper , "Alexander A. Klimov" , Masahiro Yamada Subject: Re: [PATCH v10 2/5] USB: misc: Add onboard_usb_hub driver Message-ID: <20210519144356.GB1165692@rowland.harvard.edu> References: <20210511225223.550762-1-mka@chromium.org> <20210511155152.v10.2.I7c9a1f1d6ced41dd8310e8a03da666a32364e790@changeid> <20210518194511.GA1137841@rowland.harvard.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 18, 2021 at 02:40:47PM -0700, Matthias Kaehlcke wrote: > > Could you also have a look at "[4/5] usb: host: xhci-plat: > Create platform device for onboard hubs in probe()" > (https://lore.kernel.org/patchwork/patch/1425453/)? It's a > relatively short patch that creates the platform device for > the driver from xhci-plat as you suggested in the v4 > discussion. I'm not the maintainer for xhci-related drivers. However, there is at least one thing about this patch which looks suspicious: Adding the onboard_hub_dev pointer to struct usb_hcd instead of to struct xhci_plat_priv, where it would make a lot more sense. It's also worth mentioning that this approach won't work at all when the onboard hub is not at the top level (its parent isn't the root hub), or when more than one onboard hubs are connected to the same root hub. Alan Stern