Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp1932175pxb; Wed, 20 Oct 2021 14:59:14 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy5YBq/Ysnr3XDO6j03z5B2agHB9lu9FTSYc1acONuTo7eagz71lPRo4TVajzEDPMGNZAoZ X-Received: by 2002:a17:90b:1bd2:: with SMTP id oa18mr1883368pjb.164.1634767154066; Wed, 20 Oct 2021 14:59:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1634767154; cv=none; d=google.com; s=arc-20160816; b=N5pXuB/69MY8SH5vXHAKFc0ceCy4RgGjEkOnVdyVZFTEVvEF4Z4BlcsDT8HvVCMXYh L7lMTqMaUOxM5P79zFF7KM7mCYuEXZVb+gt6X7WvjYtbDcO8llprwGkxltYS0s9VgApo 8MM22qFJwcDxo2UVzazcZ5Wgbfil2TpoC3znE2ho7jJPZWSb1CUf83mpVc9++SObqTxJ b3xSsnggy6XOPG0gXVYZgztG9ot8ATkDQyakUpK9oHp8s0i+sZhkBonIQf9GD1HCtiRv MoF/Gvc0CaYxSCvK+a4CS1y6iuS6wrx2TjjYjvUM8X/w+xTYjkCNV9+PoiCwxttqR3jR axEg== 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=ukUsrKwe2MgLI2q595S4p6KQATylJ1gix/wCNW+aA4A=; b=kf84HGNLmS272IECP6hKmcm9JtfFEphrx6CkdAjNz6lnuTtKoMnOyal2ttLcKEZ6K9 pbwqQY4FpIU5gDF4ddCoK2WqVEtjdzshLC+lvNqgomn9soeytkKO4ewed11RVXJ1o3WG 6pPVK1QdpgIE9NrvAICVwwNd0Excv1rsEkLvdvFogqgPUQhW3PgovigmBF2JLvIAKNby 9PE5s4ChqCbQFc8wFKxI+YBoVAQSwDOjeG10PGFbctJKlg9fKhYV+aIUZtHQfA359yUC gvLphi03hqBOQsIanVX+0EXjjRUd0P0QhGumb6afldtnNIAKTOD3De0+JEsvuJiY5Ns+ NSpQ== 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 s16si5003195pfu.115.2021.10.20.14.59.01; Wed, 20 Oct 2021 14:59:14 -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 S230123AbhJTV7y (ORCPT + 99 others); Wed, 20 Oct 2021 17:59:54 -0400 Received: from netrider.rowland.org ([192.131.102.5]:40851 "HELO netrider.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S229695AbhJTV7x (ORCPT ); Wed, 20 Oct 2021 17:59:53 -0400 Received: (qmail 1140230 invoked by uid 1000); 20 Oct 2021 17:57:38 -0400 Date: Wed, 20 Oct 2021 17:57:38 -0400 From: Alan Stern To: Matthias Kaehlcke Cc: Mathias Nyman , Greg Kroah-Hartman , Rob Herring , Frank Rowand , Mathias Nyman , Felipe Balbi , devicetree@vger.kernel.org, Peter Chen , linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org, Bastien Nocera , Ravi Chandra Sadineni , Michal Simek , Douglas Anderson , Roger Quadros , Krzysztof Kozlowski , Stephen Boyd , Dmitry Osipenko , Fabio Estevam Subject: Re: [PATCH v16 6/7] usb: host: xhci-plat: Create platform device for onboard hubs in probe() Message-ID: <20211020215738.GA1140001@rowland.harvard.edu> References: <20210813195228.2003500-1-mka@chromium.org> <20210813125146.v16.6.I7a3a7d9d2126c34079b1cab87aa0b2ec3030f9b7@changeid> <20211020203720.GA1137200@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 Wed, Oct 20, 2021 at 02:01:21PM -0700, Matthias Kaehlcke wrote: > On Wed, Oct 20, 2021 at 04:37:20PM -0400, Alan Stern wrote: > > On Wed, Oct 20, 2021 at 01:27:40PM -0700, Matthias Kaehlcke wrote: > > > Hi Mathias, > > > > > > On Wed, Oct 20, 2021 at 04:05:37PM +0300, Mathias Nyman wrote: > > > > If separate devices for controlling onboard hub power is the right solution then > > > > how about creating the onboard hub device in usb_add_hcd() (hcd.c), and > > > > store it in struct usb_hcd. > > > > > > > > A bit like how the roothub device is created, or PHYs are tuned. > > > > > > Sure, that sounds feasible, even better if it's handled in a single place > > > and different types of controllers don't have to add support separately. > > > > Bear in mind that this would prevent you from working with onboard > > non-root hubs. > > My goal is to (architecturally) support nested hubs, but TBH I haven't > looked much into such a configuration since I don't have hardware for > testing. My assumption was that support for onboard hubs connected to > non-root hubs whould have to be added to the generic hub driver. > > Could you elaborate in how far you think it would be different for > xhci_plat vs generic hcd? A lot of this material has slipped from my mind. However, I don't see much difference between those two approaches. Alan Stern