[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0df2fd83-951c-d253-6494-3b70f5762aae@linaro.org>
Date: Tue, 3 May 2022 17:57:52 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: "Marty E. Plummer" <hanetzer@...rtmail.com>
Cc: arnd@...db.de, cai.huoqing@...ux.dev, christian.koenig@....com,
devicetree@...r.kernel.org, gengdongjiu@...wei.com,
krzysztof.kozlowski+dt@...aro.org,
linux-arm-kernel@...ts.infradead.org, linux-clk@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mtd@...ts.infradead.org,
linux@...linux.org.uk, michael@...le.cc, miquel.raynal@...tlin.com,
mturquette@...libre.com, novikov@...ras.ru, olof@...om.net,
p.yadav@...com, rdunlap@...radead.org, richard@....at,
robh+dt@...nel.org, sboyd@...nel.org, soc@...nel.org,
sumit.semwal@...aro.org, tudor.ambarus@...rochip.com,
vigneshr@...com, xuwei5@...ilicon.com
Subject: Re: [RFC v2 2/2] arm: hisi: enable Hi3521a soc
On 03/05/2022 17:51, Marty E. Plummer wrote:
>>>> A bit weird interrupts... the same?
>>>>
>>> Yes, though I am aware that some sp804 timers do have a separate
>>> interrupts per pair.
>>
>> They have also separate interrupts, one combined interrupt or one sole
>> interrupt. However what you described here is one interrupt line
>> physically connected to two separate pins on the device yet still not
>> being somehow shared (shared as "combined interrupt"). I don't think it
>> is your case...
>>
> Unsure. datasheet just says '33 | Timer0/Timer1'. I don't think these
> timers are attached to pins, however.
So it looks like a combined interrupt, doesn't it?
Best regards,
Krzysztof
Powered by blists - more mailing lists