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=-4.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=unavailable 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 8289FC46477 for ; Mon, 17 Jun 2019 12:32:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5B9A02084D for ; Mon, 17 Jun 2019 12:32:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1560774742; bh=qBSBAULMCiLqb3om+WlEZJbnQF42E4a35DytJRXh3d0=; h=From:To:Cc:Subject:In-Reply-To:References:Date:List-ID:From; b=UBynBMYXkByedW3p2f3i6IR1/WDA78bHuEefwkDxzusAJTRToYqAutuFU3kGt4azI DC6qv43qvqWO1+w5KVFPFdAg/lBzo5qh8CkhtC+W6G7+vpJKby3l7D8OTlXmTybCzz Uj4/NLoZht2RaIdB8tlZFPGOgG3Qk91W4NzsyX9M= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726243AbfFQMcS (ORCPT ); Mon, 17 Jun 2019 08:32:18 -0400 Received: from mga12.intel.com ([192.55.52.136]:57562 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726005AbfFQMcS (ORCPT ); Mon, 17 Jun 2019 08:32:18 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Jun 2019 05:32:17 -0700 X-ExtLoop1: 1 Received: from pipin.fi.intel.com (HELO pipin) ([10.237.72.175]) by orsmga005.jf.intel.com with ESMTP; 17 Jun 2019 05:32:13 -0700 From: Felipe Balbi To: Lee Jones , alokc@codeaurora.org, agross@kernel.org, david.brown@linaro.org, wsa+renesas@sang-engineering.com, bjorn.andersson@linaro.org, gregkh@linuxfoundation.org, ard.biesheuvel@linaro.org, jlhugo@gmail.com Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org, linux-usb@vger.kernel.org Subject: Re: [PATCH v4 4/6] usb: dwc3: qcom: Add support for booting with ACPI In-Reply-To: <20190617102146.GG16364@dell> References: <20190612142654.9639-1-lee.jones@linaro.org> <20190612142654.9639-5-lee.jones@linaro.org> <20190617102146.GG16364@dell> Date: Mon, 17 Jun 2019 15:32:07 +0300 Message-ID: <87y320gzp4.fsf@linux.intel.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Sender: linux-gpio-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi, Lee Jones writes: >> In Linux, the DWC3 core exists as its own independent platform device. >> Thus when describing relationships in Device Tree, the current default >> boot configuration table option, the DWC3 core often resides as a child >> of the platform specific node. Both of which are given their own >> address space descriptions and the drivers can be mostly agnostic to >> each other. >>=20 >> However, other Operating Systems have taken a more monolithic approach, >> which is evident in the configuration ACPI tables for the Qualcomm >> Snapdragon SDM850, where all DWC3 (core and platform) components are >> described under a single IO memory region. >>=20 >> To ensure successful booting using the supplied ACPI tables, we need to >> devise a way to chop up the address regions provided and subsequently >> register the DWC3 core with the resultant information, which is >> precisely what this patch aims to achieve. >>=20 >> Signed-off-by: Lee Jones >> Reviewed-by: Bjorn Andersson >> --- >> drivers/usb/dwc3/Kconfig | 2 +- >> drivers/usb/dwc3/dwc3-qcom.c | 206 ++++++++++++++++++++++++++++++----- >> 2 files changed, 179 insertions(+), 29 deletions(-) > > I'm starting to get a little twitchy about these patches now. Due to > the release cadence of the larger Linux distros, it's pretty important > that these changes land in v5.3. Without them, it is impossible to > install Linux on some pretty high profile emerging platforms. > > It's already -rc5 and I'm concerned that we're going to miss the > merge-window. Would you be kind enough to review these patches > please? The Pinctrl and I2C parts of the set have already been > merged. I don't seem to have this series in my inbox. This is the only email I have in this series. =2D-=20 balbi --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEElLzh7wn96CXwjh2IzL64meEamQYFAl0HiEkACgkQzL64meEa mQZgTg/+MvWLo+0fVFNR04KSqTX6nZcqLk/4KwBc7uy1RsD4WMFa3zcKE/jB8scd KN48Szwr6TxXj6/nboP7PeKF+u2ftbYw8L1Ggtd1Okq/Fn8mUcM+vY1xGotjgrao ZXbOLcI393gCADUuEgHbOZDXPeLtgF2K/RQ06CPJ+wPunpx3pDwJVaMumW5Inocu Yz/eMkd5XP2QXDfL8F+27ZfnZQ6oNbEa+RV0cakbyvjHWDbkeiCW2DN5YFM3gJpC T9RXeqzKIUkfWd3mLcBq54Z3wCh51nw2UfThE1bQK2XlPKPXnU9P/Oi7ZIJYn5X4 hF9PoBRoYWoaS5v9TJxL+78F+salna/FVsr6jKtbmVQjr4t3H+2i3SKXUmcMtaP9 /jXg8jRCni44640ri7F4xN52TdkE/K7eAShOTp2izyRydKkZRxCOgW0xPh1Yi6Yx DGFxy4TQPUc6uAchzWfB/DIQywLYMDChFGMc525vTiw3ATnWf5dK7c/G0FufNs+g YcXsD9HyhYs9puAp4DBUZmXZGiuPHT8Se78aTfYqAvY7oFH5puh2Mg8UDLeeiatr A67I1jpWh9RvTGFPpBABobbaItB4lMcitFy2MqxByxNmJt9l5bbExTRmdXLFzbZK db8+BiVaO0xw70s0j9BuGwO/YolXOiX2i4lP4Qzhc7WjniL3FPw= =l8qE -----END PGP SIGNATURE----- --=-=-=--