On 27/01/2017 22:03, Rob Herring wrote:
On Tue, Jan 24, 2017 at 03:05:23PM +0800, zhichang.yuan wrote:
There are some special ISA/LPC devices that work on a specific I/O range where
it is not correct to specify a 'ranges' property in DTS parent node as cpu
addresses translated from DTS node are
On Mon, Jan 30, 2017 at 9:57 AM, John Garry wrote:
> On 27/01/2017 22:03, Rob Herring wrote:
>> On Tue, Jan 24, 2017 at 03:05:23PM +0800, zhichang.yuan wrote:
>>> Signed-off-by: zhichang.yuan
>>> Signed-off-by: Gabriele Paoloni
>>> Signed-off-by: Arnd Bergmann
>>
>>
>> Shouldn't this be Reviewe
On Tue, Jan 24, 2017 at 03:05:23PM +0800, zhichang.yuan wrote:
> There are some special ISA/LPC devices that work on a specific I/O range where
> it is not correct to specify a 'ranges' property in DTS parent node as cpu
> addresses translated from DTS node are only for memory space on some
> archi
There are some special ISA/LPC devices that work on a specific I/O range where
it is not correct to specify a 'ranges' property in DTS parent node as cpu
addresses translated from DTS node are only for memory space on some
architectures, such as Arm64. Without the parent 'ranges' property, current
4 matches
Mail list logo
