From: Thierry Reding <thierry.reding@gmail.com>
To: Sowjanya Komatineni <skomatineni@nvidia.com>
Cc: adrian.hunter@intel.com, ulf.hansson@linaro.org,
jonathanh@nvidia.com, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: Re: [PATCH V7 1/2] arm64: dtsi: Fix SDMMC address range
Date: Thu, 10 Jan 2019 15:47:31 +0100 [thread overview]
Message-ID: <20190110144731.GA25353@ulmo> (raw)
In-Reply-To: <1546457808-18270-2-git-send-email-skomatineni@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1843 bytes --]
On Wed, Jan 02, 2019 at 11:36:47AM -0800, Sowjanya Komatineni wrote:
> This patch fixes the SDMMC Controllers address space to be exact
> defined register address range as per the design.
>
> SDMMC Controller supporting Command Queue has CQHCI registers at
> offset 0xF000.
>
> This fix helps to identify the Tegra SDMMC Controllers supporting
> Command Queue based on the size of address space.
>
> Signed-off-by: Sowjanya Komatineni <skomatineni@nvidia.com>
> ---
> arch/arm64/boot/dts/nvidia/tegra186.dtsi | 6 +++---
> arch/arm64/boot/dts/nvidia/tegra194.dtsi | 4 ++--
> 2 files changed, 5 insertions(+), 5 deletions(-)
After applying these patches I'm having second thoughts about the DT
aspect of this. I know you and Timo had originally argued to advertise
the capability via an extra property in DT instead of updating the reg
property. In retrospect, I think that's the right thing to do, after
all.
The problem I'm running into is that if I apply patch 2/2 without the
first patch, then both Jetson TX2 and Jetson AGX Xavier crash on boot
because they try to access these registers (the I/O memory size is
0x10000 for all controllers). So we're effectively breaking ABI with
existing device trees.
I don't know of a way to work around that other than the separate
property. Would you mind changing the series to contain:
1) a patch updating the device tree bindings with the new
optional property that would mark SDMMC4 as CQE capable
(make sure to Cc devicetree@vger.kernel.org on that patch)
2) replace this patch by one which only adds the new
"supports-cqe" property
3) update the second patch to make the decision based on the
flag rather than the I/O memory size
Sorry for the back and forth on this. I evidently hadn't thought this
through.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-01-10 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 19:36 [PATCH V7 0/2] HW Command Queue support for Tegra SDMMC Sowjanya Komatineni
2019-01-02 19:36 ` [PATCH V7 1/2] arm64: dtsi: Fix SDMMC address range Sowjanya Komatineni
2019-01-10 14:47 ` Thierry Reding [this message]
2019-01-02 19:36 ` [PATCH V7 2/2] mmc: tegra: HW Command Queue Support for Tegra SDMMC Sowjanya Komatineni
2019-01-10 13:17 ` Adrian Hunter
2019-01-11 0:34 ` Sowjanya Komatineni
2019-01-15 3:10 ` Chunyan Zhang
2019-01-15 3:26 ` Sowjanya Komatineni
2019-01-10 15:12 ` Thierry Reding
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=20190110144731.GA25353@ulmo \
--to=thierry.reding@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=skomatineni@nvidia.com \
--cc=ulf.hansson@linaro.org \
/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).