All of lore.kernel.org
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4] arm64: amd-seattle: Adding device tree for AMD Seattle platform
Date: Thu, 27 Nov 2014 14:45:26 +0000	[thread overview]
Message-ID: <54773906.5030504@arm.com> (raw)
In-Reply-To: <20141127142811.GN828@e106497-lin.cambridge.arm.com>

On 27/11/14 14:28, Liviu Dudau wrote:
> On Tue, Nov 25, 2014 at 11:46:50AM +0000, Suthikulpanit, Suravee wrote:
>> Hi Marc,
>>
>> On 11/25/14, 17:23, "Marc Zyngier" <marc.zyngier@arm.com> wrote:
>>
>>> Hi Suravee,
>>>
>>> Just spotted a small issue below (looks like a recurring mistake in a
>>> number of DTs I've seem lately):
>>>
>>> On 24/11/14 21:51, suravee.suthikulpanit at amd.com wrote:
>>>> From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
>>>>
>>>> Initial revision of device tree for AMD Seattle platform.
>>>>
>>>> Cc: Arnd Bergmann <arnd@arndb.de>
>>>> Cc: Marc Zyngier <marc.zyngier@arm.com>
>>>> Cc: Mark Rutland <mark.rutland@arm.com>
>>>> Cc: Will Deacon <will.deacon@arm.com>
>>>> Cc: Catalin Marinas <catalin.marinas@arm.com>
>>>> Signed-off-by: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
>>>> Signed-off-by: Thomas Lendacky <Thomas.Lendacky@amd.com>
>>>> Signed-off-by: Joel Schopp <Joel.Schopp@amd.com>
>>>> ---
>>>> V4 Changes:
>>>>     * Remove unnecessary smb layer and move motherbord to top level
>>>>     * Move include dtsi to top level
>>>>     * Remove apb_pclk from sata0 and i2c
>>>>     * Fix GIC Virtual Maintanance Interrupt from PPI24 (8) to PPI25 (9)
>>>>     * Add 40-bit dma-ranges for motherboard (simple-bus)
>>>>     * Remove dma0 (pl330) entry for now since it only supports 32-bit
>>>> DMA.
>>>>       It is basically not used at the moment. It would also need SMMU
>>>>       to allow dma remapping to 40-bit DMA range.
>>>>     * Add phandle spi0 and spi1
>>>>     * Hook up gpio0 pin 7 with MMC Card Detection (CD) support.
>>>>     * Changes in pcie0 entry:
>>>>         - Add 40-bit dma-ranges
>>>>         - Remove interrupts property
>>>>         - Add interrupt-map/mask property
>>>>         - Fix PCI I/O range
>>>>         - Merge PCI 32-bit ranges
>>>>         - Merge PCI 64-bit ranges
>>>>
>>>> NOTE: I am not add a new compatible ID for the sata0 as Rob Herring
>>>>       suggested since there is no need at the momement, and I am trying
>>>>       to avoid introducing ID unnecessarily.
>>>>
>>>>  arch/arm64/Kconfig                          |   5 +
>>>>  arch/arm64/boot/dts/Makefile                |   1 +
>>>>  arch/arm64/boot/dts/amd-seattle-periph.dtsi | 156
>>>> ++++++++++++++++++++++++++++
>>>>  arch/arm64/boot/dts/amd-seattle.dts         |  89 ++++++++++++++++
>>>>  4 files changed, 251 insertions(+)
>>>>  create mode 100644 arch/arm64/boot/dts/amd-seattle-periph.dtsi
>>>>  create mode 100644 arch/arm64/boot/dts/amd-seattle.dts
>>>>
>>>
>>> [...]
>>>
>>>> diff --git a/arch/arm64/boot/dts/amd-seattle.dts
>>>> b/arch/arm64/boot/dts/amd-seattle.dts
>>>> new file mode 100644
>>>> index 0000000..d5fc482
>>>> --- /dev/null
>>>> +++ b/arch/arm64/boot/dts/amd-seattle.dts
>>>> @@ -0,0 +1,89 @@
>>>> +/*
>>>> + * DTS file for AMD Seattle
>>>> + *
>>>> + * Copyright (C) 2014 Advanced Micro Devices, Inc.
>>>> + */
>>>> +
>>>> +/dts-v1/;
>>>> +
>>
>> [...] 
>>
>>>> +
>>>> +	timer {
>>>> +		compatible = "arm,armv8-timer";
>>>> +		interrupts = <1 13 0xff01>,
>>>> +			     <1 14 0xff01>,
>>>> +			     <1 11 0xff01>,
>>>> +			     <1 10 0xff01>;
>>>> +	};
>>>
>>> The Cortex-A57 TRM clearly states that these interrupts are level
>>> triggered.
>>
>> Thanks for pointing this out. I?ll fix this to <1 1X 0xff04> (4 for the
>> Active-High) then.
> 
> Hi Suravee,
> 
> Don't know what Seattle does, but the TRM says that the outputs are active-LOW.

As I said in another thread, 0xff04 *is* the right value. This is an
interrupt descriptor for the GIC, not a qualifier for the signal that
comes out of the core.

Thanks.

	M.
-- 
Jazz is not dead. It just smells funny...

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <marc.zyngier@arm.com>
To: Liviu Dudau <Liviu.Dudau@arm.com>,
	"suravee.suthikulpanit@amd.com" <suravee.suthikulpanit@amd.com>
Cc: "arnd@arndb.de" <arnd@arndb.de>,
	Mark Rutland <Mark.Rutland@arm.com>,
	Will Deacon <Will.Deacon@arm.com>,
	Catalin Marinas <Catalin.Marinas@arm.com>,
	"robherring2@gmail.com" <robherring2@gmail.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"arm@kernel.org" <arm@kernel.org>,
	"Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
	"Schopp, Joel" <Joel.Schopp@amd.com>
Subject: Re: [PATCH V4] arm64: amd-seattle: Adding device tree for AMD Seattle platform
Date: Thu, 27 Nov 2014 14:45:26 +0000	[thread overview]
Message-ID: <54773906.5030504@arm.com> (raw)
In-Reply-To: <20141127142811.GN828@e106497-lin.cambridge.arm.com>

On 27/11/14 14:28, Liviu Dudau wrote:
> On Tue, Nov 25, 2014 at 11:46:50AM +0000, Suthikulpanit, Suravee wrote:
>> Hi Marc,
>>
>> On 11/25/14, 17:23, "Marc Zyngier" <marc.zyngier@arm.com> wrote:
>>
>>> Hi Suravee,
>>>
>>> Just spotted a small issue below (looks like a recurring mistake in a
>>> number of DTs I've seem lately):
>>>
>>> On 24/11/14 21:51, suravee.suthikulpanit@amd.com wrote:
>>>> From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
>>>>
>>>> Initial revision of device tree for AMD Seattle platform.
>>>>
>>>> Cc: Arnd Bergmann <arnd@arndb.de>
>>>> Cc: Marc Zyngier <marc.zyngier@arm.com>
>>>> Cc: Mark Rutland <mark.rutland@arm.com>
>>>> Cc: Will Deacon <will.deacon@arm.com>
>>>> Cc: Catalin Marinas <catalin.marinas@arm.com>
>>>> Signed-off-by: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
>>>> Signed-off-by: Thomas Lendacky <Thomas.Lendacky@amd.com>
>>>> Signed-off-by: Joel Schopp <Joel.Schopp@amd.com>
>>>> ---
>>>> V4 Changes:
>>>>     * Remove unnecessary smb layer and move motherbord to top level
>>>>     * Move include dtsi to top level
>>>>     * Remove apb_pclk from sata0 and i2c
>>>>     * Fix GIC Virtual Maintanance Interrupt from PPI24 (8) to PPI25 (9)
>>>>     * Add 40-bit dma-ranges for motherboard (simple-bus)
>>>>     * Remove dma0 (pl330) entry for now since it only supports 32-bit
>>>> DMA.
>>>>       It is basically not used at the moment. It would also need SMMU
>>>>       to allow dma remapping to 40-bit DMA range.
>>>>     * Add phandle spi0 and spi1
>>>>     * Hook up gpio0 pin 7 with MMC Card Detection (CD) support.
>>>>     * Changes in pcie0 entry:
>>>>         - Add 40-bit dma-ranges
>>>>         - Remove interrupts property
>>>>         - Add interrupt-map/mask property
>>>>         - Fix PCI I/O range
>>>>         - Merge PCI 32-bit ranges
>>>>         - Merge PCI 64-bit ranges
>>>>
>>>> NOTE: I am not add a new compatible ID for the sata0 as Rob Herring
>>>>       suggested since there is no need at the momement, and I am trying
>>>>       to avoid introducing ID unnecessarily.
>>>>
>>>>  arch/arm64/Kconfig                          |   5 +
>>>>  arch/arm64/boot/dts/Makefile                |   1 +
>>>>  arch/arm64/boot/dts/amd-seattle-periph.dtsi | 156
>>>> ++++++++++++++++++++++++++++
>>>>  arch/arm64/boot/dts/amd-seattle.dts         |  89 ++++++++++++++++
>>>>  4 files changed, 251 insertions(+)
>>>>  create mode 100644 arch/arm64/boot/dts/amd-seattle-periph.dtsi
>>>>  create mode 100644 arch/arm64/boot/dts/amd-seattle.dts
>>>>
>>>
>>> [...]
>>>
>>>> diff --git a/arch/arm64/boot/dts/amd-seattle.dts
>>>> b/arch/arm64/boot/dts/amd-seattle.dts
>>>> new file mode 100644
>>>> index 0000000..d5fc482
>>>> --- /dev/null
>>>> +++ b/arch/arm64/boot/dts/amd-seattle.dts
>>>> @@ -0,0 +1,89 @@
>>>> +/*
>>>> + * DTS file for AMD Seattle
>>>> + *
>>>> + * Copyright (C) 2014 Advanced Micro Devices, Inc.
>>>> + */
>>>> +
>>>> +/dts-v1/;
>>>> +
>>
>> [...] 
>>
>>>> +
>>>> +	timer {
>>>> +		compatible = "arm,armv8-timer";
>>>> +		interrupts = <1 13 0xff01>,
>>>> +			     <1 14 0xff01>,
>>>> +			     <1 11 0xff01>,
>>>> +			     <1 10 0xff01>;
>>>> +	};
>>>
>>> The Cortex-A57 TRM clearly states that these interrupts are level
>>> triggered.
>>
>> Thanks for pointing this out. I¹ll fix this to <1 1X 0xff04> (4 for the
>> Active-High) then.
> 
> Hi Suravee,
> 
> Don't know what Seattle does, but the TRM says that the outputs are active-LOW.

As I said in another thread, 0xff04 *is* the right value. This is an
interrupt descriptor for the GIC, not a qualifier for the signal that
comes out of the core.

Thanks.

	M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2014-11-27 14:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 21:51 [PATCH V4] arm64: amd-seattle: Adding device tree for AMD Seattle platform suravee.suthikulpanit at amd.com
2014-11-24 21:51 ` suravee.suthikulpanit
2014-11-24 23:09 ` Olof Johansson
2014-11-24 23:09   ` Olof Johansson
2014-11-25  8:38   ` Suthikulpanit, Suravee
2014-11-25  8:38     ` Suthikulpanit, Suravee
2014-11-25 10:23 ` Marc Zyngier
2014-11-25 10:23   ` Marc Zyngier
2014-11-25 11:46   ` Suthikulpanit, Suravee
2014-11-25 11:46     ` Suthikulpanit, Suravee
2014-11-27 14:28     ` Liviu Dudau
2014-11-27 14:28       ` Liviu Dudau
2014-11-27 14:45       ` Marc Zyngier [this message]
2014-11-27 14:45         ` Marc Zyngier
2014-11-25 11:57 ` Arnd Bergmann
2014-11-25 11:57   ` Arnd Bergmann
2014-11-25 20:39   ` Suthikulpanit, Suravee
2014-11-25 20:39     ` Suthikulpanit, Suravee

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=54773906.5030504@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.