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 X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E7ACBC433E1 for ; Tue, 18 Aug 2020 11:04:41 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id B66D02067C for ; Tue, 18 Aug 2020 11:04:41 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="rnsD6AzA"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="Xz+KBqCs" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B66D02067C Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linuxfoundation.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References:Message-ID: Subject:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=/pz/4xD6kMaQiRGy3AqNGUczP/ybIGlffcDudzo+wYg=; b=rnsD6AzAMf1bAOOv700jj+GjO BYS+PAmCDpTm5QkdGtAcWdT6L0Cxj16SgFbD0wCM9zdO7xLD9O3ERQYmWjMabpVl2FIdO0ewniubh 6EEbEjsYhRCSH+y/OCJYYFv6QOi1n28QUxCckS3j/P3h6+R2PzLdB+RGVaMk3deBZaO5uH04BJ7xQ WC5eehvuh1HssNH9Fueqr4AusUiAVfGI17n0JKiJYaQszYqSVsxj21YW5nfwS1GxHjHVcuSc0ziVM UsMHs0ZdzZPgF5Cj0Jx6j1RhfXFe4kJhDs9nf6T9AdFJ7CeiDahVZs8j9JzBiLlTuA8cHjITMgRUQ XY0xFPxlw==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1k7zOo-0008HI-CL; Tue, 18 Aug 2020 11:03:26 +0000 Received: from mail.kernel.org ([198.145.29.99]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1k7zOl-0008Ge-IU; Tue, 18 Aug 2020 11:03:24 +0000 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id B109C2067C; Tue, 18 Aug 2020 11:03:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1597748602; bh=aM76h0LVRWD/VLaNlIvaLamCRS32rZ9tXaBBf7SqjKM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Xz+KBqCsqtyyNaFLl9EC9cWvB075M+HVY4v7aNwfI6vFva6s2DbNBy3ym7dpepa/G ODNgxQ8gjopHuSd1fg0KlxpT1DTBAl5NUYCcNKBK4VRJBV73kd6osQAXp161bnqMrQ F66WXUNy9iNq54bXz8NiYpLKpBYgjX8be+T77SVM= Date: Tue, 18 Aug 2020 13:03:32 +0200 From: Greg KH To: Nicolas Saenz Julienne Subject: Re: [PATCH v5 0/9] Raspberry Pi 4 USB firmware initialization rework Message-ID: <20200818110332.GA167428@kroah.com> References: <20200629161845.6021-1-nsaenzjulienne@suse.de> <01e4b87c-d287-fd72-9f9c-545539127a50@gmail.com> <20200814061105.GG1409566@kroah.com> <21baf85fa476f62a56895d77fa76dc0d73c1b3a0.camel@suse.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <21baf85fa476f62a56895d77fa76dc0d73c1b3a0.camel@suse.de> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200818_070323_769037_EE2A474C X-CRM114-Status: GOOD ( 26.60 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: robh@kernel.org, Florian Fainelli , mathias.nyman@linux.intel.com, linux-pci@vger.kernel.org, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, andy.shevchenko@gmail.com, tim.gover@raspberrypi.org, bcm-kernel-feedback-list@broadcom.com, wahrenst@gmx.net, p.zabel@pengutronix.de, helgaas@kernel.org, lorenzo.pieralisi@arm.com, linux-arm-kernel@lists.infradead.org, linux-rpi-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, Aug 14, 2020 at 12:04:05PM +0200, Nicolas Saenz Julienne wrote: > On Fri, 2020-08-14 at 08:11 +0200, Greg KH wrote: > > On Thu, Aug 13, 2020 at 12:17:49PM -0700, Florian Fainelli wrote: > > > > > > On 8/13/2020 3:01 AM, Nicolas Saenz Julienne wrote: > > > > Hi everyone. > > > > > > > > On Mon, 2020-06-29 at 18:18 +0200, Nicolas Saenz Julienne wrote: > > > > > On the Raspberry Pi 4, after a PCI reset, VL805's firmware may either be > > > > > loaded directly from an EEPROM or, if not present, by the SoC's > > > > > co-processor, VideoCore. This series reworks how we handle this. > > > > > > > > > > The previous solution makes use of PCI quirks and exporting platform > > > > > specific functions. Albeit functional it feels pretty shoehorned. This > > > > > proposes an alternative way of handling the triggering of the xHCI chip > > > > > initialization trough means of a reset controller. > > > > > > > > > > The benefits are pretty evident: less platform churn in core xHCI code, > > > > > and no explicit device dependency management in pcie-brcmstb. > > > > > > > > > > Note that patch #1 depends on another series[1], that was just applied > > > > > into the clk maintainer's tree. > > > > > > > > > > The series is based on v5.8-rc3 > > > > > > > > > > v3: https://www.spinics.net/lists/arm-kernel/msg813612.html > > > > > v2: https://lkml.org/lkml/2020/6/9/875 > > > > > v1: https://lore.kernel.org/linux-usb/20200608192701.18355-1-nsaenzjulienne@suse.de/T/#t > > > > > > > > > > [1] https://lore.kernel.org/linux-clk/159304773261.62212.983376627029743900@swboyd.mtv.corp.google.com/T/#t > > > > > > > > > > --- > > > > > > > > We were waiting on a dependency to be merged upstream to get this. They are now > > > > in, so could we move things forward? > > > > > > > > I can take the device tree patches, I guess philipp can take the reset > > > > controller code. But I'm not so sure who should be taking the PCI/USB > > > > counterparts. > > > > > > Should we route everything through the USB tree since that is where the > > > changes that do require synchronization with other subsystems and DTS is > > > needed the most? > > > -- > > > Florian > > > > That's fine with me, if everyone else is ok with it :) > > Sounds good to me. All now queued up, thanks for sticking with this! greg k-h _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel