From: Lee Jones <lee.jones@linaro.org>
To: Felipe Balbi <balbi@kernel.org>
Cc: 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, 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
Date: Mon, 17 Jun 2019 13:43:29 +0100 [thread overview]
Message-ID: <20190617124329.GH16364@dell> (raw)
In-Reply-To: <87y320gzp4.fsf@linux.intel.com>
On Mon, 17 Jun 2019, Felipe Balbi wrote:
> Hi,
>
> Lee Jones <lee.jones@linaro.org> 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.
> >>
> >> 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.
> >>
> >> 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.
> >>
> >> Signed-off-by: Lee Jones <lee.jones@linaro.org>
> >> Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> >> ---
> >> 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.
I did wonder, which is why I made sure I sent this to your Intel
address as well. Is your @kernel.org address broken?
Will re-send the patches to your Intel address, give me a few
minutes.
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2019-06-17 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190612142654.9639-1-lee.jones@linaro.org>
[not found] ` <20190612142654.9639-5-lee.jones@linaro.org>
2019-06-17 10:21 ` [PATCH v4 4/6] usb: dwc3: qcom: Add support for booting with ACPI Lee Jones
2019-06-17 12:32 ` Felipe Balbi
2019-06-17 12:43 ` Lee Jones [this message]
2019-06-17 12:45 ` Felipe Balbi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190617124329.GH16364@dell \
--to=lee.jones@linaro.org \
--cc=agross@kernel.org \
--cc=alokc@codeaurora.org \
--cc=ard.biesheuvel@linaro.org \
--cc=balbi@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jlhugo@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).