Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp124541ybk; Fri, 8 May 2020 15:52:43 -0700 (PDT) X-Google-Smtp-Source: APiQypLL0wRrDrQ73ULAUdDgysm2SX7f9n3TFHOPDJ84PuyfPhNud+KPfBBcFBtfQc4t6+MUVFnq X-Received: by 2002:a05:6402:1596:: with SMTP id c22mr4434712edv.100.1588978363470; Fri, 08 May 2020 15:52:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588978363; cv=none; d=google.com; s=arc-20160816; b=nVpFrryI3WbZInPhWY5XbFySI004V8PBe565PCIrDjlaraXHM2wLNJu5GpU0LmkeOU L0id9ja9GK6qNa7s5TycTl/3E1eNXi5IIOzX+b72yVjVgCBMEM3T8pvXQ0VVqx0USKVD 9z/AefYtynOE2RvNdRC4j9ozHk3KpCOWu6TB2ClL6YP5tgmXysOBizmOhkCEXEfZgE53 zSr06/zHMs9xF/FhbEo886JlP3yO+MqRCiSER7PTxUt9+MLNRmOtmgyxfwo5YuwKOR2k 64F/3WbIY2CzQO+lyO8tMlOHpPfo/DdlbnurvLovQM+VQ0bT7skqqm7nAIJ0uHKoNGxu l0YQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=V3nc4NBSeZ0B9rUqgxGAX48Rma2M/iKEjSutkviGE4Q=; b=IE1eqUNM8kpfigo0d0b96V+t9NHS6Avdq195vD2W+fkJIMOxjdB5nmSA5IKQozhadO /wRYhRXJfW90CshJzLP8jNSs5j4tDWXNkSBblJW5QzsxbFmWyky5tQwRKB29kG8CwrWs iNj+J2JEl+0H9j11PuH6tV8clsWvNGJiNLud+ulHo6hZNxnPxfNOdGqgXjTBRAp1h+qv 2zdL3ezYwESMhtIMkcIQLViZ5TDmQk4mEOzPTgjLpus9m/cEvnZ/RejFTOibzf4ETVDN hfhxd1xl+41uc9hROI2No2skH9wAeBy7vfby8sDfmV8Evad0nLmtriuE7a3If5mfVawb hrLg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Rbdz2xcr; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dn15si1716054edb.555.2020.05.08.15.52.20; Fri, 08 May 2020 15:52:43 -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; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Rbdz2xcr; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727899AbgEHWu6 (ORCPT + 99 others); Fri, 8 May 2020 18:50:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42188 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1727774AbgEHWu6 (ORCPT ); Fri, 8 May 2020 18:50:58 -0400 Received: from mail-wr1-x444.google.com (mail-wr1-x444.google.com [IPv6:2a00:1450:4864:20::444]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A472FC061A0C; Fri, 8 May 2020 15:50:57 -0700 (PDT) Received: by mail-wr1-x444.google.com with SMTP id s8so3744559wrt.9; Fri, 08 May 2020 15:50:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=V3nc4NBSeZ0B9rUqgxGAX48Rma2M/iKEjSutkviGE4Q=; b=Rbdz2xcrk8vpCyPDyAgfbsmQ8rl7ctSx/u0Q/RXDgSP+qyWCYVkMEEA5FGk1FFHlMu 0rG/+L7W3uqMRXEtCtPcoq0/VFYPz3BjOoM6ArXS4d4GVxmFIUhmCb4371XIeKm3TbNn jmQ/Hz1FEOMOV/gkqny9GJ9Y0UDgRhrnVsuzsCEMpSYX1Xm7fJKtaAZhOZW182ssoRhM vsqEtUjrKKqYGptTR+2Sk5lkS9Tz6Zi045IQCRGDjRu7SuV/us7o+kbop7E5cGyz45dS 3OXpIP9pqSEJjdmekc5kpnvljSQmOlq9Mggx/Zfkc1BWcRDZG7LBJLr6LrP57IyCv5xG 7TLA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=V3nc4NBSeZ0B9rUqgxGAX48Rma2M/iKEjSutkviGE4Q=; b=JxXp3UsiJsMbGtIPl7IxkFHA+BX0YdlMmwQZafROpKBsqbo5r4mf4D7NhzyY1DR7lI 4pcP6xLUlj/s83p8n22AOArhpXP1av4TGu1jsrj8BRwjnz1ljevB9GGT3LiYVTNvMRUU lkpVi+e/8LU0mLlyB9/ztrN6+bTj1VFX0WAbCYjm0zuKFyZUvYvreX98frgbLV2HO4zB TirTKfICf2600f5SHtn/WMzC0gCvLhWvQflPfbRRPlGEpGIe+dZS7MRgNPyIOFYTmix+ oGfVUpElDcQUsiaBh0Gz0gfH9jFZ1AJ+Cpp59PAcQPLZyV3zoeySdGHZKcfVkJMuGrMN 5D7w== X-Gm-Message-State: AGi0PuY8uTdZH4+4VInLuC34LwgcQ9uHiMZrdFNVhQ/q8ND/MYXBk+GQ MMvN6Vk1f3VWNcRJREO1Gf0= X-Received: by 2002:adf:ea44:: with SMTP id j4mr5797953wrn.38.1588978256310; Fri, 08 May 2020 15:50:56 -0700 (PDT) Received: from [10.230.188.43] ([192.19.223.252]) by smtp.gmail.com with ESMTPSA id u67sm3429631wmu.3.2020.05.08.15.50.53 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 08 May 2020 15:50:55 -0700 (PDT) Subject: Re: [PATCH v8 1/5] usb: xhci: Change the XHCI link order in the Makefile To: Al Cooper , linux-kernel@vger.kernel.org Cc: Alan Stern , Andy Shevchenko , bcm-kernel-feedback-list@broadcom.com, devicetree@vger.kernel.org, Greg Kroah-Hartman , Krzysztof Kozlowski , linux-usb@vger.kernel.org, Mathias Nyman , Rob Herring , Yoshihiro Shimoda , Andy Shevchenko References: <20200508211929.39020-1-alcooperx@gmail.com> <20200508211929.39020-2-alcooperx@gmail.com> From: Florian Fainelli Message-ID: <39262358-9ba5-20f7-656b-63825da369d6@gmail.com> Date: Fri, 8 May 2020 15:50:51 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Firefox/68.0 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: <20200508211929.39020-2-alcooperx@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 5/8/2020 2:19 PM, Al Cooper wrote: > Some BRCMSTB USB chips have an XHCI, EHCI and OHCI controller > on the same port where XHCI handles 3.0 devices, EHCI handles 2.0 > devices and OHCI handles <2.0 devices. Currently the Makefile > has XHCI linking at the bottom which will result in the XHIC driver > initalizing after the EHCI and OHCI drivers and any installed 3.0 > device will be seen as a 2.0 device. Moving the XHCI linking > above the EHCI and OHCI linking fixes the issue. > > Signed-off-by: Al Cooper Reviewed-by: Florian Fainelli -- Florian