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 X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 23DD1C28D16 for ; Mon, 10 Jun 2019 10:21:04 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id F132920859 for ; Mon, 10 Jun 2019 10:21:03 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="NnLT/vHj" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389360AbfFJKVD (ORCPT ); Mon, 10 Jun 2019 06:21:03 -0400 Received: from mail-vs1-f66.google.com ([209.85.217.66]:34919 "EHLO mail-vs1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388937AbfFJKVC (ORCPT ); Mon, 10 Jun 2019 06:21:02 -0400 Received: by mail-vs1-f66.google.com with SMTP id u124so4976831vsu.2 for ; Mon, 10 Jun 2019 03:21:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SP4C91hkmfb8nf4pEfeOT8GgXw6uPbDXmSTuJCq/gGc=; b=NnLT/vHjyOBGZwlrcg6VlzgOH161C3LeV8WVy/Vu8rFpi3c/FRWMWJAgX1juq3HdBx L8SvJdLZ3DJYOGXVVqnaHEP5aYAPVqmD06tmeB37f8Zd2tJkwL3EEk9U+CyW/i2cGMDn /qbzJ3ipIzTlfQIz/Ku+Z+csNl5SVYR0z0h06poDeKOV3bCxAQ4+UPlvkgzYF3sHr6PW fNIwoN7cDHj1MRQI75Wh16WPHdavqxIdQxDViUCNbS748aaCS+CSALai5WJM95xeE+Le 5WlgNvBWmNkP0+IZOmesajCOvIc6FGL6UJrFm0O3ov8s+u1/KMEO8G01o2byn1gEeC98 E3dg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SP4C91hkmfb8nf4pEfeOT8GgXw6uPbDXmSTuJCq/gGc=; b=XM/DWT1NKtx/BXHwKhV+Vpb/IWbegqb7NmzAtpDISA882+cXNI++bl9riUM92xcW1A uhRWZU8OFToFYugSRCwbJTiImGO6bX4aexnemY+PIjKn2qKtCwYLNycwRTw41cGtFLRn /lu51pnAhdun2b0L8zeo2hg3bSi12nn1bPM5XrEOJXAD3SoYtI94hBgMYw1Nf7grHy5R RlAkZjKNF3xMLPduO2Ug2dvXFz6DdCy0Qtor2pQRrnmQkmOZUYFxssJ6YipWt8WMTO0N ZEkePqiqSwIkVqh1CYshaKLomHGOm4RkKNk2hZrVnmcM27IEK545Q4HsTizOQUIWjBmY BU/w== X-Gm-Message-State: APjAAAUtSu3vUdFCKQztmwaRG+AVdgCy2E8j7utCwxMhPMTT6XFOdkmn 4VuYNdPMSg0Hf9EaYT/T/V17u7nEXCtxdvW2Pee7rg== X-Google-Smtp-Source: APXvYqyEELW5eYybi8NTzXTq1BaVxGi1afLoOiDPwggiWfgN/Ej4B4ujdWWHnp+5MIZ0eyrZ5ciJlutJA2qYMY6qJQA= X-Received: by 2002:a67:706:: with SMTP id 6mr19148665vsh.200.1560162061544; Mon, 10 Jun 2019 03:21:01 -0700 (PDT) MIME-Version: 1.0 References: <20190513192300.653-1-ulf.hansson@linaro.org> <20190513192300.653-5-ulf.hansson@linaro.org> <20190607150052.GC15577@e107155-lin> In-Reply-To: <20190607150052.GC15577@e107155-lin> From: Ulf Hansson Date: Mon, 10 Jun 2019 12:20:25 +0200 Message-ID: Subject: Re: [PATCH 04/18] ARM/ARM64: cpuidle: Let back-end init ops take the driver as input To: Sudeep Holla Cc: Lorenzo Pieralisi , Mark Rutland , Linux ARM , "Rafael J . Wysocki" , Daniel Lezcano , "Raju P . L . S . S . S . N" , Amit Kucheria , Bjorn Andersson , Stephen Boyd , Niklas Cassel , Tony Lindgren , Kevin Hilman , Lina Iyer , Viresh Kumar , Vincent Guittot , Geert Uytterhoeven , Souvik Chakravarty , Linux PM , linux-arm-msm , Linux Kernel Mailing List , Russell King , Catalin Marinas , Will Deacon , Andy Gross , David Brown Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 7 Jun 2019 at 17:01, Sudeep Holla wrote: > > On Mon, May 13, 2019 at 09:22:46PM +0200, Ulf Hansson wrote: > > To allow arch back-end init ops to operate on the cpuidle driver for the > > corresponding CPU, let's pass along a pointer to the struct cpuidle_driver* > > and forward it the relevant layers of callbacks for ARM/ARM64. > > > > I may be wrong, but I see drv is just used to get state_count mostly. > It's also used in flattening part, but that should not be here either. Let me copy the note I added below the changelog for $subject patch, as hopefully that should clarify the reason to why this is needed. "- This patch is needed by the subsequent patch, but more importantly, also by "[PATCH 10/18] drivers: firmware: psci: Add hierarchical domain idle states converter"." Kind regards Uffe