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=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no 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 72BDBC4338F for ; Wed, 25 Aug 2021 15:42:49 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 5A7FF6108F for ; Wed, 25 Aug 2021 15:42:49 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240180AbhHYPne (ORCPT ); Wed, 25 Aug 2021 11:43:34 -0400 Received: from perceval.ideasonboard.com ([213.167.242.64]:42458 "EHLO perceval.ideasonboard.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241121AbhHYPna (ORCPT ); Wed, 25 Aug 2021 11:43:30 -0400 Received: from pendragon.ideasonboard.com (62-78-145-57.bb.dnainternet.fi [62.78.145.57]) by perceval.ideasonboard.com (Postfix) with ESMTPSA id 6B18424F; Wed, 25 Aug 2021 17:42:42 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1629906162; bh=z+pGs7ptzS2pWN5a//5s422Ig5ykca/VKKLgcOkqcck=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=HpLVDgUyv9p+Lvjvv4W3jq+s+YF5NoVGTMRTEAFR8Og9jXeyuVgvon699aTEJaokF K2ymO/VhXZYP0OPhh/UBw06ZdbF1S9lIeQ9tVvRbVqyjnOZVeY5zirFMySSE2/XiVq KqiF5WvtuLk5k3lzpgciLmUimBzgzS8tBKOg6RME= Date: Wed, 25 Aug 2021 18:42:30 +0300 From: Laurent Pinchart To: Mark Brown Cc: Hans de Goede , Daniel Scally , linux-kernel@vger.kernel.org, platform-driver-x86@vger.kernel.org, Liam Girdwood , Mark Gross , Maximilian Luz , Kieran Bingham , Sakari Ailus Subject: Re: [RFC PATCH v2 1/3] regulator: core: Add regulator_lookup_list Message-ID: References: <20210824230620.1003828-1-djrscally@gmail.com> <20210824230620.1003828-2-djrscally@gmail.com> <20210825103301.GC5186@sirena.org.uk> <20210825152735.GJ5186@sirena.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20210825152735.GJ5186@sirena.org.uk> Precedence: bulk List-ID: X-Mailing-List: platform-driver-x86@vger.kernel.org On Wed, Aug 25, 2021 at 04:27:35PM +0100, Mark Brown wrote: > On Wed, Aug 25, 2021 at 04:48:15PM +0200, Hans de Goede wrote: > > > Daniel, I believe that what Mark wants here is something similar to what > > we already do for the 5v boost converter regulator in the TI bq24190 charger > > chip used on some Cherry Trail devices. > > Yeah, that or something like a generalized version of it which lets a > separate quirk file like they seem to have register the data to insert - > I'd be happy enough with the simple thing too given that it's not > visible to anything, or with DMI quirks in the regulator driver too for > that matter if it's just one or two platforms but there do seem to be > rather a lot of these platforms which need quirks. Let's also remember that we have to handle not just regulators, but also GPIOs and clocks. And I'm pretty sure there will be more. We could have a mechanism specific to the tps68470 driver to pass platform data from the board file to the driver, and replicate that mechanism in different drivers (for other regulators, clocks and GPIOs), but I really would like to avoid splitting the DMI-conditioned platform data in those drivers directly. I'd like to store all the init data for a given platform in a single "board" file. -- Regards, Laurent Pinchart