From: Arnd Bergmann <arnd@arndb.de>
To: Rob Herring <robh@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Nava kishore Manne <nava.manne@xilinx.com>,
mark.rutland@arm.com, devicetree@vger.kernel.org,
navam@xilinx.com, hyun.kwon@xilinx.com, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, gregkh@linuxfoundation.org,
radhey.shyam.pandey@xilinx.com, michal.simek@xilinx.com,
balbi@ti.com, linux-kernel@vger.kernel.org, galak@codeaurora.org,
soren.brinkmann@xilinx.com
Subject: Re: [PATCH] Axi-usb: Add support for 64-bit addressing.
Date: Mon, 18 Apr 2016 16:35:07 +0200 [thread overview]
Message-ID: <4449845.qT8BZnpD4R@wuerfel> (raw)
In-Reply-To: <20160418142909.GA5608@rob-hp-laptop>
On Monday 18 April 2016 09:29:09 Rob Herring wrote:
>
> Right, you don't need to know the exact bus width for determining the
> register/descriptor set is 32 or 64 bit addesses. I'm fine with a
> property for that, but if limiting the actual connected address bits is
> needed, then dma-ranges should be used.
The other way round: dma-ranges is needed to allow 64-bit addressing,
the default is to only allow 32-bit addressing (and arm64 has a known
bug here, it just allows it anyway when it shouldn't).
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Rob Herring <robh@kernel.org>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
navam@xilinx.com, pawel.moll@arm.com, hyun.kwon@xilinx.com,
ijc+devicetree@hellion.org.uk,
Nava kishore Manne <nava.manne@xilinx.com>,
radhey.shyam.pandey@xilinx.com, michal.simek@xilinx.com,
balbi@ti.com, linux-kernel@vger.kernel.org, galak@codeaurora.org,
soren.brinkmann@xilinx.com, gregkh@linuxfoundation.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] Axi-usb: Add support for 64-bit addressing.
Date: Mon, 18 Apr 2016 16:35:07 +0200 [thread overview]
Message-ID: <4449845.qT8BZnpD4R@wuerfel> (raw)
In-Reply-To: <20160418142909.GA5608@rob-hp-laptop>
On Monday 18 April 2016 09:29:09 Rob Herring wrote:
>
> Right, you don't need to know the exact bus width for determining the
> register/descriptor set is 32 or 64 bit addesses. I'm fine with a
> property for that, but if limiting the actual connected address bits is
> needed, then dma-ranges should be used.
The other way round: dma-ranges is needed to allow 64-bit addressing,
the default is to only allow 32-bit addressing (and arm64 has a known
bug here, it just allows it anyway when it shouldn't).
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Axi-usb: Add support for 64-bit addressing.
Date: Mon, 18 Apr 2016 16:35:07 +0200 [thread overview]
Message-ID: <4449845.qT8BZnpD4R@wuerfel> (raw)
In-Reply-To: <20160418142909.GA5608@rob-hp-laptop>
On Monday 18 April 2016 09:29:09 Rob Herring wrote:
>
> Right, you don't need to know the exact bus width for determining the
> register/descriptor set is 32 or 64 bit addesses. I'm fine with a
> property for that, but if limiting the actual connected address bits is
> needed, then dma-ranges should be used.
The other way round: dma-ranges is needed to allow 64-bit addressing,
the default is to only allow 32-bit addressing (and arm64 has a known
bug here, it just allows it anyway when it shouldn't).
Arnd
next prev parent reply other threads:[~2016-04-18 14:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 7:41 [PATCH] Axi-usb: Add support for 64-bit addressing Nava kishore Manne
2016-04-11 7:41 ` Nava kishore Manne
2016-04-11 7:41 ` Nava kishore Manne
2016-04-11 8:08 ` kbuild test robot
2016-04-11 8:08 ` kbuild test robot
2016-04-11 8:08 ` kbuild test robot
2016-04-17 14:09 ` Arnd Bergmann
2016-04-17 14:09 ` Arnd Bergmann
2016-04-12 14:03 ` Rob Herring
2016-04-12 14:03 ` Rob Herring
2016-04-17 13:14 ` Arnd Bergmann
2016-04-17 13:14 ` Arnd Bergmann
2016-04-18 14:29 ` Rob Herring
2016-04-18 14:29 ` Rob Herring
2016-04-18 14:29 ` Rob Herring
2016-04-18 14:35 ` Arnd Bergmann [this message]
2016-04-18 14:35 ` Arnd Bergmann
2016-04-18 14:35 ` Arnd Bergmann
2016-04-19 9:15 ` Nava kishore Manne
2016-04-19 9:15 ` Nava kishore Manne
2016-04-19 9:15 ` Nava kishore Manne
2016-04-19 14:07 ` Arnd Bergmann
2016-04-19 14:07 ` Arnd Bergmann
2016-04-19 14:07 ` Arnd Bergmann
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=4449845.qT8BZnpD4R@wuerfel \
--to=arnd@arndb.de \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=hyun.kwon@xilinx.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=nava.manne@xilinx.com \
--cc=navam@xilinx.com \
--cc=pawel.moll@arm.com \
--cc=radhey.shyam.pandey@xilinx.com \
--cc=robh@kernel.org \
--cc=soren.brinkmann@xilinx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.