From: Yingjoe Chen <yingjoe.chen@mediatek.com> To: Doug Anderson <dianders@chromium.org> Cc: Sonny Rao <sonnyrao@chromium.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, Mark Rutland <Mark.Rutland@arm.com>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>, "pawel.moll@arm.com" <pawel.moll@arm.com>, "ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>, Marc Zyngier <marc.zyngier@arm.com>, Catalin Marinas <catalin.marinas@arm.com>, Daniel Lezcano <daniel.lezcano@linaro.org>, Will Deacon <will.deacon@arm.com>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "robh+dt@kernel.org" <robh+dt@kernel.org>, "galak@codeaurora.org" <galak@codeaurora.org>, Sudeep Holla <Sudeep.Holla@arm.com>, Olof Johansson <olof@lixom.net>, Nathan Lynch <Nathan_Lynch@mentor.com>, Thomas Gleixner <tglx@linutronix.de>, Stephen Boyd <sboyd@codeaurora.org> Subject: Re: [PATCH v4] clocksource: arch_timer: Allow the device tree to specify uninitialized timer registers Date: Thu, 27 Nov 2014 10:27:04 +0800 [thread overview] Message-ID: <1417055224.12707.24.camel@mtksdaap41> (raw) In-Reply-To: <CAD=FV=XFcWEp=nZ3=8QEausKzpBbPCzFUSHY-g0K5y+VPpU3Vw@mail.gmail.com> Hi, On Wed, 2014-11-26 at 08:14 -0800, Doug Anderson wrote: > Yingjoe, > > On Wed, Nov 26, 2014 at 6:41 AM, Yingjoe Chen <yingjoe.chen@mediatek.com> wrote: > > Sorry for the (very) late reply. > > I just realize today MT8135 need this and the other patch [1] to boot > > SMP correctly. I've applied both patches and they works fine. Thanks :) > > Excellent. It's helpful to include a Tested-by: tag in your email. > You'd have a line with just "Tested-by: Yingjoe Chen > <yingjoe.chen@mediatek.com>" sure, here's my tested-by for the 2 patches Tested-by: Yingjoe Chen <yingjoe.chen@mediatek.com> I'll remember to add it next time :) > > However, I'm not sure if we really need to add new property. > > arm_arch_timer driver will only use virtual timer when virtual PPI > > interrupt is provided, so the following patch to timer dtsi will also > > works. I think if the firmware doesn't support virtual timer, it make > > sense to not supply virtual interrupt. > > > > timer { > > compatible = "arm,armv7-timer"; > > interrupts = <GIC_PPI 13 IRQ_TYPE_LEVEL_LOW>, > > - <GIC_PPI 14 IRQ_TYPE_LEVEL_LOW>, > > - <GIC_PPI 11 IRQ_TYPE_LEVEL_LOW>, > > - <GIC_PPI 10 IRQ_TYPE_LEVEL_LOW>; > > + <GIC_PPI 14 IRQ_TYPE_LEVEL_LOW>; > > clock-frequency = <13000000>; > > }; > > Once you have Sonny's patch then I believe that the above would work. > However we rejected something like this because device tree is > supposed to describe the hardware. The hardware really does provide > the virtual timer interrupts and they really are at PPI 11 and PPI 10. > It's just that firmware doesn't handle things properly so they can't > be used. > > NOTE: If we add the "arm,cpu-registers-not-fw-configured" to the > device tree and firmware actually works out how to configure things > (like if somehow has firmware that has a hypervisor) then it can > easily remove this device tree property before calling through to the > kernel. It would be much harder for the firmware to add back in the > "PPI 11" and "PPI 10" entries to the timer. > > -Doug I see your point, that's good for me then. Thanks. Joe.C
WARNING: multiple messages have this Message-ID (diff)
From: yingjoe.chen@mediatek.com (Yingjoe Chen) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v4] clocksource: arch_timer: Allow the device tree to specify uninitialized timer registers Date: Thu, 27 Nov 2014 10:27:04 +0800 [thread overview] Message-ID: <1417055224.12707.24.camel@mtksdaap41> (raw) In-Reply-To: <CAD=FV=XFcWEp=nZ3=8QEausKzpBbPCzFUSHY-g0K5y+VPpU3Vw@mail.gmail.com> Hi, On Wed, 2014-11-26 at 08:14 -0800, Doug Anderson wrote: > Yingjoe, > > On Wed, Nov 26, 2014 at 6:41 AM, Yingjoe Chen <yingjoe.chen@mediatek.com> wrote: > > Sorry for the (very) late reply. > > I just realize today MT8135 need this and the other patch [1] to boot > > SMP correctly. I've applied both patches and they works fine. Thanks :) > > Excellent. It's helpful to include a Tested-by: tag in your email. > You'd have a line with just "Tested-by: Yingjoe Chen > <yingjoe.chen@mediatek.com>" sure, here's my tested-by for the 2 patches Tested-by: Yingjoe Chen <yingjoe.chen@mediatek.com> I'll remember to add it next time :) > > However, I'm not sure if we really need to add new property. > > arm_arch_timer driver will only use virtual timer when virtual PPI > > interrupt is provided, so the following patch to timer dtsi will also > > works. I think if the firmware doesn't support virtual timer, it make > > sense to not supply virtual interrupt. > > > > timer { > > compatible = "arm,armv7-timer"; > > interrupts = <GIC_PPI 13 IRQ_TYPE_LEVEL_LOW>, > > - <GIC_PPI 14 IRQ_TYPE_LEVEL_LOW>, > > - <GIC_PPI 11 IRQ_TYPE_LEVEL_LOW>, > > - <GIC_PPI 10 IRQ_TYPE_LEVEL_LOW>; > > + <GIC_PPI 14 IRQ_TYPE_LEVEL_LOW>; > > clock-frequency = <13000000>; > > }; > > Once you have Sonny's patch then I believe that the above would work. > However we rejected something like this because device tree is > supposed to describe the hardware. The hardware really does provide > the virtual timer interrupts and they really are at PPI 11 and PPI 10. > It's just that firmware doesn't handle things properly so they can't > be used. > > NOTE: If we add the "arm,cpu-registers-not-fw-configured" to the > device tree and firmware actually works out how to configure things > (like if somehow has firmware that has a hypervisor) then it can > easily remove this device tree property before calling through to the > kernel. It would be much harder for the firmware to add back in the > "PPI 11" and "PPI 10" entries to the timer. > > -Doug I see your point, that's good for me then. Thanks. Joe.C
next prev parent reply other threads:[~2014-11-27 2:27 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-08 7:33 [PATCH v4] clocksource: arch_timer: Allow the device tree to specify uninitialized timer registers Sonny Rao 2014-10-08 7:33 ` Sonny Rao 2014-10-08 7:33 ` Sonny Rao 2014-11-19 23:01 ` Doug Anderson 2014-11-19 23:01 ` Doug Anderson 2014-11-19 23:01 ` Doug Anderson 2014-11-23 21:41 ` Daniel Lezcano 2014-11-23 21:41 ` Daniel Lezcano 2014-11-23 21:41 ` Daniel Lezcano 2014-11-26 11:51 ` Daniel Lezcano 2014-11-26 11:51 ` Daniel Lezcano 2014-11-26 12:06 ` Heiko Stübner 2014-11-26 12:06 ` Heiko Stübner 2014-11-26 12:06 ` Heiko Stübner 2014-11-26 12:30 ` Daniel Lezcano 2014-11-26 12:30 ` Daniel Lezcano 2014-11-26 12:30 ` Daniel Lezcano 2014-11-26 12:48 ` Heiko Stübner 2014-11-26 12:48 ` Heiko Stübner 2014-11-26 12:48 ` Heiko Stübner 2014-11-26 12:49 ` Daniel Lezcano 2014-11-26 12:49 ` Daniel Lezcano 2014-11-26 12:49 ` Daniel Lezcano 2014-11-26 12:55 ` Heiko Stübner 2014-11-26 12:55 ` Heiko Stübner 2014-11-26 12:55 ` Heiko Stübner 2014-11-26 12:53 ` Daniel Lezcano 2014-11-26 12:53 ` Daniel Lezcano 2014-11-26 12:53 ` Daniel Lezcano 2014-11-26 12:49 ` Daniel Lezcano 2014-11-26 12:49 ` Daniel Lezcano 2014-11-28 14:16 ` Catalin Marinas 2014-11-28 14:16 ` Catalin Marinas 2014-11-28 14:16 ` Catalin Marinas 2014-11-26 14:41 ` Yingjoe Chen 2014-11-26 14:41 ` Yingjoe Chen 2014-11-26 14:41 ` Yingjoe Chen 2014-11-26 16:14 ` Doug Anderson 2014-11-26 16:14 ` Doug Anderson 2014-11-26 16:14 ` Doug Anderson 2014-11-27 2:27 ` Yingjoe Chen [this message] 2014-11-27 2:27 ` Yingjoe Chen 2014-11-27 2:27 ` Yingjoe Chen 2014-12-05 7:34 ` Olof Johansson 2014-12-05 7:34 ` Olof Johansson 2014-12-05 7:34 ` Olof Johansson
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=1417055224.12707.24.camel@mtksdaap41 \ --to=yingjoe.chen@mediatek.com \ --cc=Mark.Rutland@arm.com \ --cc=Nathan_Lynch@mentor.com \ --cc=Sudeep.Holla@arm.com \ --cc=catalin.marinas@arm.com \ --cc=daniel.lezcano@linaro.org \ --cc=devicetree@vger.kernel.org \ --cc=dianders@chromium.org \ --cc=galak@codeaurora.org \ --cc=ijc+devicetree@hellion.org.uk \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=lorenzo.pieralisi@arm.com \ --cc=marc.zyngier@arm.com \ --cc=olof@lixom.net \ --cc=pawel.moll@arm.com \ --cc=robh+dt@kernel.org \ --cc=sboyd@codeaurora.org \ --cc=sonnyrao@chromium.org \ --cc=tglx@linutronix.de \ --cc=will.deacon@arm.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: linkBe 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.