From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id D1B50C43334 for ; Thu, 23 Jun 2022 13:20:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=aR1L0VhPJDzZA2l8rq4Az1H/62HV+wJ9kosDX7Lzse4=; b=lmApVib4zKOC4/ fkynKkvqkPSGIPxsOz5w116JgH1apXPjLzzsHNjnpYrxjobTlHlHK0T+B5mZpdQL9SiDY+s+7LvIa d8/GlCFfmPwxcyathcj4rNy7lOTmRvKcouHXURh/MFFsT0646YOxB8e95M1OYzxh/KHYgwg84yQfs iD4vwpjJBZSiyjyxIULsH+Y59N5cHSmBcaLV16JtSR6lF+JDEgTw91ksCCF+KF4uElDHu9i/PEVIS nByqQPJMe470bivKgm4zJpA7hg2mVtxx+BbBkYm5rh52mPW2Dw8OATwTVkTFr3TT6Y/8kPW+l3I4O anvmtGYaPSk002S3ed9w==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1o4Mjt-00FIzB-Qm; Thu, 23 Jun 2022 13:19:17 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1o4Mjq-00FIyE-Cg for linux-arm-kernel@lists.infradead.org; Thu, 23 Jun 2022 13:19:15 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id F008D61CEE; Thu, 23 Jun 2022 13:19:12 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 948E9C341C4; Thu, 23 Jun 2022 13:19:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1655990352; bh=ncg899RK9f+f5Z0KZ/AxsbE694mnUgGJh3xSzIgIgsI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=uJOAkmsVQioytc3R9Tq/vWOmqUHR/zUaiilHD/ZxUfFuDblgrReUdhOac6B30GMiH Nav+0JJfW0xK11Ks092NJ41K5Az/fop4wYgOEpCjTyr3EGETA/vIqMmrnHAWAEc1vx JGtmmc6uGhdZFTVq3HJemtJhPvN3azwxQ8GXGcrFtUOHRUg4crVZU2wMeoQirfnBSp ZsCD6JNPZl69anKxkGNsQdIGVXxRd/mfJGxrppniIeB+0W5+fRjkbAQ+GreG+Jr1uA nVraVmzulz+6SN8psQ37WYaC507n+zyBRYqyBzEuXRK1rq/DrZM3OVzsbRAkVk+zRb MoLvINaQCe7NQ== Date: Thu, 23 Jun 2022 14:19:06 +0100 From: Will Deacon To: Sudeep Holla Cc: Michael Walle , Catalin Marinas , Lorenzo Pieralisi , Daniel Lezcano , "Rafael J . Wysocki" , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org Subject: Re: [PATCH 0/2] arm64: remove generic ARM cpuidle support Message-ID: <20220623131906.GA16222@willie-the-truck> References: <20220529181329.2345722-1-michael@walle.cc> <09f392794c815cbfb38e5103d92310da@walle.cc> <20220622140748.laklytigxtfdbbg2@bogus> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20220622140748.laklytigxtfdbbg2@bogus> User-Agent: Mutt/1.10.1 (2018-07-13) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220623_061914_509005_19269628 X-CRM114-Status: GOOD ( 25.94 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, Jun 22, 2022 at 03:07:48PM +0100, Sudeep Holla wrote: > On Wed, Jun 22, 2022 at 01:59:07PM +0200, Michael Walle wrote: > > Am 2022-05-29 20:13, schrieb Michael Walle: > > > Playing with an own PSCI implementation, I've noticed that the > > > cpuidle-arm > > > driver doesn't work on arm64. It doesn't probe because since commit > > > 788961462f34 ("ARM: psci: cpuidle: Enable PSCI CPUidle driver") the > > > arm_cpuidle_init() can only return -EOPNOTSUPP, because the commit > > > removed > > > the cpu_idle_init and cpu_suspend ops. > > > > > > It left me puzzled for quite some time. It seems that the cpuidle-psci > > > is > > > the preferred one and this has been the case for quite some time. The > > > mentioned commit first appeared in v5.4. > > > > > > Remove the ARM64 support for the cpuidle-arm driver, which then let us > > > remove all the supporting arch code. > > > > > > Michael Walle (2): > > > cpuidle: cpuidle-arm: remove arm64 support > > > arm64: cpuidle: remove generic cpuidle support > > > > > > arch/arm64/include/asm/cpu_ops.h | 9 --------- > > > arch/arm64/include/asm/cpuidle.h | 15 --------------- > > > arch/arm64/kernel/cpuidle.c | 29 ----------------------------- > > > drivers/cpuidle/Kconfig.arm | 3 ++- > > > 4 files changed, 2 insertions(+), 54 deletions(-) > > > > Through which tree should this patchset go? I've seen it is marked as > > "Handled Elsewere" in the linux pm patchwork [1]. > > > > Generally based on the changes, it is decided. I can see why Rafael would > have marked so in PM patchwork. Daniel has already acked small change in > CPUidle config file while the bulk is removal of arm64 code. So, it is > better to route it via arm64 tree. > > Will, > > Assuming you will handle v5.20, can you pick this up ? Yup, on it. Will _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel