From: Abel Vesa <abel.vesa@nxp.com> To: Martin Kepplinger <martink@posteo.de> Cc: Leonard Crestez <leonard.crestez@nxp.com>, Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>, Rob Herring <robh+dt@kernel.org>, Mark Rutland <mark.rutland@arm.com>, Shawn Guo <shawnguo@kernel.org>, Sascha Hauer <s.hauer@pengutronix.de>, Pengutronix Kernel Team <kernel@pengutronix.de>, Fabio Estevam <festevam@gmail.com>, Thomas Gleixner <tglx@linutronix.de>, Marc Zyngier <marc.zyngier@arm.com>, Lucas Stach <l.stach@pengutronix.de>, Jacky Bai <ping.bai@nxp.com>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, Carlo Caione <ccaione@baylibre.com>, dl-linux-imx <linux-imx@nxp.com>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org> Subject: Re: [RFC 0/2] Add workaround for core wake-up on IPI for i.MX8MQ Date: Fri, 8 Nov 2019 11:50:03 +0000 [thread overview] Message-ID: <20191108115002.cqzvpxydzwos64vp@fsr-ub1664-175> (raw) In-Reply-To: <c3519156-9769-980b-d9e7-af372ced8797@posteo.de> On 19-11-08 12:21:21, Martin Kepplinger wrote: > Hi Leonard, hi Abel, > > Thanks for having a look! To sum up this problem and not to get confused: > > We have the workaround that changes irq-imx-gpcv2 from this very email > thread, to be used with mainline ATF. when applying Abel's recent diff, > Linux 5.4 boots but I still don't have a cpuidle driver. > > When I enable CONFIG_ARM_PSCI_CPUIDLE, the kernel hangs during boot > (after probing mmc, but that doesn't tell much) > > What do I miss? > OK, please fetch the branches called "imx8mq-err11171" from both following github repos and give it a try: https://github.com/abelvesa/linux.git and https://github.com/abelvesa/arm-trusted-firmware.git I just tested it. Works with defconfig. > > Then (in parallel) we have NXP's ATF: > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsource.codeaurora.org%2Fexternal%2Fimx%2Fimx-atf%2Flog%2F%3Fh%3Dimx_4.19.35_1.0.0&data=02%7C01%7Cabel.vesa%40nxp.com%7C0a5a09f616c84932e06d08d7643dccaf%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637088088896134121&sdata=tq0aUGawG%2FhRRXZB9jdIi2xSNGHINhbWM1ZpDKPFrqU%3D&reserved=0 > that I test in parallel (and will actually want to have cpuidle right > now too). The workaround in Linux in that case looks like so: > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsource.codeaurora.org%2Fexternal%2Fimx%2Flinux-imx%2Fcommit%2F%3Fh%3Dimx_4.19.35_1.0.0%26id%3D26a59057f88997dfe48ab7f81898ddd6b6d3903e&data=02%7C01%7Cabel.vesa%40nxp.com%7C0a5a09f616c84932e06d08d7643dccaf%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637088088896134121&sdata=GqmtzpS8fB4bxmOXxTNQZrWNCV18lNu7XpX5dmcAEaY%3D&reserved=0 > which changes irq-gic-v3 only. > Forget about the NXP arm-trusted-firmware for now. It will never work with mainline + the workaround patches. > Since 5.4, also no cpu-sleep state anymore. What would need to change in > that "NXP" case, for 5.4 to have cpuidle again? > > When I enable ARM_PSCI_CPUIDLE here, right now Linux hangs during boot > (during probing sdhci but again that seems random). > > I'm still happy for hints :) > > Thanks, > > martin >
WARNING: multiple messages have this Message-ID (diff)
From: Abel Vesa <abel.vesa@nxp.com> To: Martin Kepplinger <martink@posteo.de> Cc: Mark Rutland <mark.rutland@arm.com>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>, Jacky Bai <ping.bai@nxp.com>, Carlo Caione <ccaione@baylibre.com>, Marc Zyngier <marc.zyngier@arm.com>, Fabio Estevam <festevam@gmail.com>, Sascha Hauer <s.hauer@pengutronix.de>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>, dl-linux-imx <linux-imx@nxp.com>, Pengutronix Kernel Team <kernel@pengutronix.de>, Thomas Gleixner <tglx@linutronix.de>, Leonard Crestez <leonard.crestez@nxp.com>, Shawn Guo <shawnguo@kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, Lucas Stach <l.stach@pengutronix.de> Subject: Re: [RFC 0/2] Add workaround for core wake-up on IPI for i.MX8MQ Date: Fri, 8 Nov 2019 11:50:03 +0000 [thread overview] Message-ID: <20191108115002.cqzvpxydzwos64vp@fsr-ub1664-175> (raw) In-Reply-To: <c3519156-9769-980b-d9e7-af372ced8797@posteo.de> On 19-11-08 12:21:21, Martin Kepplinger wrote: > Hi Leonard, hi Abel, > > Thanks for having a look! To sum up this problem and not to get confused: > > We have the workaround that changes irq-imx-gpcv2 from this very email > thread, to be used with mainline ATF. when applying Abel's recent diff, > Linux 5.4 boots but I still don't have a cpuidle driver. > > When I enable CONFIG_ARM_PSCI_CPUIDLE, the kernel hangs during boot > (after probing mmc, but that doesn't tell much) > > What do I miss? > OK, please fetch the branches called "imx8mq-err11171" from both following github repos and give it a try: https://github.com/abelvesa/linux.git and https://github.com/abelvesa/arm-trusted-firmware.git I just tested it. Works with defconfig. > > Then (in parallel) we have NXP's ATF: > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsource.codeaurora.org%2Fexternal%2Fimx%2Fimx-atf%2Flog%2F%3Fh%3Dimx_4.19.35_1.0.0&data=02%7C01%7Cabel.vesa%40nxp.com%7C0a5a09f616c84932e06d08d7643dccaf%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637088088896134121&sdata=tq0aUGawG%2FhRRXZB9jdIi2xSNGHINhbWM1ZpDKPFrqU%3D&reserved=0 > that I test in parallel (and will actually want to have cpuidle right > now too). The workaround in Linux in that case looks like so: > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsource.codeaurora.org%2Fexternal%2Fimx%2Flinux-imx%2Fcommit%2F%3Fh%3Dimx_4.19.35_1.0.0%26id%3D26a59057f88997dfe48ab7f81898ddd6b6d3903e&data=02%7C01%7Cabel.vesa%40nxp.com%7C0a5a09f616c84932e06d08d7643dccaf%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637088088896134121&sdata=GqmtzpS8fB4bxmOXxTNQZrWNCV18lNu7XpX5dmcAEaY%3D&reserved=0 > which changes irq-gic-v3 only. > Forget about the NXP arm-trusted-firmware for now. It will never work with mainline + the workaround patches. > Since 5.4, also no cpu-sleep state anymore. What would need to change in > that "NXP" case, for 5.4 to have cpuidle again? > > When I enable ARM_PSCI_CPUIDLE here, right now Linux hangs during boot > (during probing sdhci but again that seems random). > > I'm still happy for hints :) > > Thanks, > > martin > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-11-08 11:50 UTC|newest] Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-10 12:13 [RFC 0/2] Add workaround for core wake-up on IPI for i.MX8MQ Abel Vesa 2019-06-10 12:13 ` Abel Vesa 2019-06-10 12:13 ` Abel Vesa 2019-06-10 12:13 ` [RFC 1/2] irqchip: irq-imx-gpcv2: Add workaround for i.MX8MQ ERR11171 Abel Vesa 2019-06-10 12:13 ` Abel Vesa 2019-06-10 12:38 ` Leonard Crestez 2019-06-10 12:38 ` Leonard Crestez 2019-06-10 12:38 ` Leonard Crestez 2019-06-10 13:24 ` Marc Zyngier 2019-06-10 13:24 ` Marc Zyngier 2019-06-10 13:38 ` Abel Vesa 2019-06-10 13:38 ` Abel Vesa 2019-06-10 13:38 ` Abel Vesa 2019-06-10 13:51 ` Marc Zyngier 2019-06-10 13:51 ` Marc Zyngier 2019-06-10 13:51 ` Marc Zyngier 2019-06-10 14:12 ` Abel Vesa 2019-06-10 14:12 ` Abel Vesa 2019-06-10 14:12 ` Abel Vesa 2019-06-10 14:28 ` Marc Zyngier 2019-06-10 14:28 ` Marc Zyngier 2019-06-10 14:28 ` Marc Zyngier 2019-06-10 12:13 ` [RFC 2/2] arm64: dts: imx8mq: Add idle states and gpcv2 wake_request broken property Abel Vesa 2019-06-10 12:13 ` Abel Vesa 2019-06-10 13:19 ` [RFC 0/2] Add workaround for core wake-up on IPI for i.MX8MQ Mark Rutland 2019-06-10 13:19 ` Mark Rutland 2019-06-10 13:29 ` Abel Vesa 2019-06-10 13:29 ` Abel Vesa 2019-06-10 13:29 ` Abel Vesa 2019-06-10 13:39 ` Marc Zyngier 2019-06-10 13:39 ` Marc Zyngier 2019-06-10 13:39 ` Marc Zyngier 2019-06-10 13:55 ` Abel Vesa 2019-06-10 13:55 ` Abel Vesa 2019-06-10 13:55 ` Abel Vesa 2019-06-10 14:07 ` Marc Zyngier 2019-06-10 14:07 ` Marc Zyngier 2019-06-10 14:07 ` Marc Zyngier 2019-06-10 14:32 ` Leonard Crestez 2019-06-10 14:32 ` Leonard Crestez 2019-06-10 14:32 ` Leonard Crestez 2019-06-10 14:52 ` Marc Zyngier 2019-06-10 14:52 ` Marc Zyngier 2019-06-10 14:52 ` Marc Zyngier 2019-06-12 7:14 ` Thomas Gleixner 2019-06-12 7:14 ` Thomas Gleixner 2019-06-12 7:14 ` Thomas Gleixner 2019-06-12 7:35 ` Marc Zyngier 2019-06-12 7:35 ` Marc Zyngier 2019-06-12 7:35 ` Marc Zyngier 2019-06-12 7:37 ` Thomas Gleixner 2019-06-12 7:37 ` Thomas Gleixner 2019-06-12 7:37 ` Thomas Gleixner 2019-06-23 11:47 ` Martin Kepplinger 2019-06-23 11:47 ` Martin Kepplinger 2019-06-28 8:54 ` Abel Vesa 2019-06-28 8:54 ` Abel Vesa 2019-06-28 8:54 ` Abel Vesa 2019-07-02 6:47 ` Martin Kepplinger 2019-07-02 6:47 ` Martin Kepplinger 2019-07-02 6:47 ` Martin Kepplinger 2019-07-02 11:33 ` Abel Vesa 2019-07-02 11:33 ` Abel Vesa 2019-07-02 11:33 ` Abel Vesa 2019-07-08 7:54 ` Martin Kepplinger 2019-07-08 7:54 ` Martin Kepplinger 2019-07-08 7:54 ` Martin Kepplinger 2019-07-08 12:20 ` Martin Kepplinger 2019-07-08 12:20 ` Martin Kepplinger 2019-07-08 12:20 ` Martin Kepplinger 2019-10-30 6:11 ` Martin Kepplinger 2019-10-30 6:11 ` Martin Kepplinger 2019-10-30 7:33 ` Martin Kepplinger 2019-10-30 7:33 ` Martin Kepplinger 2019-10-30 8:08 ` Abel Vesa 2019-10-30 8:08 ` Abel Vesa 2019-10-30 8:14 ` Martin Kepplinger 2019-10-30 8:14 ` Martin Kepplinger 2019-11-04 8:49 ` Martin Kepplinger 2019-11-04 8:49 ` Martin Kepplinger 2019-11-04 10:35 ` Abel Vesa 2019-11-04 10:35 ` Abel Vesa 2019-11-06 11:59 ` Martin Kepplinger 2019-11-06 11:59 ` Martin Kepplinger 2019-11-06 22:36 ` Leonard Crestez 2019-11-06 22:36 ` Leonard Crestez 2019-11-08 11:21 ` Martin Kepplinger 2019-11-08 11:21 ` Martin Kepplinger 2019-11-08 11:50 ` Abel Vesa [this message] 2019-11-08 11:50 ` Abel Vesa 2019-11-08 14:17 ` Martin Kepplinger 2019-11-08 14:17 ` Martin Kepplinger 2019-11-11 7:54 ` Abel Vesa 2019-11-11 7:54 ` Abel Vesa 2019-11-25 17:23 ` Martin Kepplinger 2019-11-25 17:23 ` Martin Kepplinger
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=20191108115002.cqzvpxydzwos64vp@fsr-ub1664-175 \ --to=abel.vesa@nxp.com \ --cc=ccaione@baylibre.com \ --cc=devicetree@vger.kernel.org \ --cc=festevam@gmail.com \ --cc=kernel@pengutronix.de \ --cc=l.stach@pengutronix.de \ --cc=leonard.crestez@nxp.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-imx@nxp.com \ --cc=linux-kernel@vger.kernel.org \ --cc=lorenzo.pieralisi@arm.com \ --cc=marc.zyngier@arm.com \ --cc=mark.rutland@arm.com \ --cc=martink@posteo.de \ --cc=ping.bai@nxp.com \ --cc=robh+dt@kernel.org \ --cc=s.hauer@pengutronix.de \ --cc=shawnguo@kernel.org \ --cc=tglx@linutronix.de \ /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.