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.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED 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 32A9AC433DF for ; Tue, 9 Jun 2020 15:30:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 10E1C2072F for ; Tue, 9 Jun 2020 15:30:25 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=walle.cc header.i=@walle.cc header.b="Jsr8QG9b" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730797AbgFIPaT (ORCPT ); Tue, 9 Jun 2020 11:30:19 -0400 Received: from ssl.serverraum.org ([176.9.125.105]:54073 "EHLO ssl.serverraum.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729027AbgFIPaS (ORCPT ); Tue, 9 Jun 2020 11:30:18 -0400 Received: from ssl.serverraum.org (web.serverraum.org [172.16.0.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ssl.serverraum.org (Postfix) with ESMTPSA id C2CE522F54; Tue, 9 Jun 2020 17:30:06 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walle.cc; s=mail2016061301; t=1591716613; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=5fW2eer9+yY8UigSBRZj7sU8vGtoK3CaYKgnjiJ9Ftc=; b=Jsr8QG9bQvMRxi+JC3zJF6oiNPIPFthDgRXmHE3KezcDNOYyGUNV5OAImGBlHMGL5NTMyg H61bpzBx9wXe1ekcEpZqZYGS5xGzM6j4pfJFpVrh2WZlKjhi6EkYz4iooa0zHfzpMmPgpi Bv61N/8jh4hOE6c5nIppCvTW9O67BKs= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 09 Jun 2020 17:30:06 +0200 From: Michael Walle To: Lee Jones Cc: Andy Shevchenko , Ranjani Sridharan , david.m.ertman@intel.com, shiraz.saleem@intel.com, Rob Herring , Mark Brown , "open list:GPIO SUBSYSTEM" , devicetree , Linux Kernel Mailing List , linux-hwmon@vger.kernel.org, linux-pwm@vger.kernel.org, linux-watchdog@vger.kernel.org, linux-arm Mailing List , Linus Walleij , Bartosz Golaszewski , Jean Delvare , Guenter Roeck , Thierry Reding , =?UTF-8?Q?Uwe_Kleine-K?= =?UTF-8?Q?=C3=B6nig?= , Wim Van Sebroeck , Shawn Guo , Li Yang , Thomas Gleixner , Jason Cooper , Marc Zyngier , Greg Kroah-Hartman , Andy Shevchenko Subject: Re: [PATCH v4 02/11] mfd: Add support for Kontron sl28cpld management controller In-Reply-To: <20200609151941.GM4106@dell> References: <20200606114645.GB2055@sirena.org.uk> <20200608082827.GB3567@dell> <7d7feb374cbf5a587dc1ce65fc3ad672@walle.cc> <20200608185651.GD4106@dell> <32231f26f7028d62aeda8fdb3364faf1@walle.cc> <20200609064735.GH4106@dell> <32287ac0488f7cbd5a7d1259c284e554@walle.cc> <20200609151941.GM4106@dell> User-Agent: Roundcube Webmail/1.4.4 Message-ID: <95e6ec9bbdf6af7a9ff9c31786f743f2@walle.cc> X-Sender: michael@walle.cc Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org Am 2020-06-09 17:19, schrieb Lee Jones: > On Tue, 09 Jun 2020, Michael Walle wrote: > >> Am 2020-06-09 08:47, schrieb Lee Jones: >> > On Mon, 08 Jun 2020, Michael Walle wrote: >> > >> > > Am 2020-06-08 20:56, schrieb Lee Jones: >> > > > On Mon, 08 Jun 2020, Michael Walle wrote: >> > > > >> > > > > Am 2020-06-08 12:02, schrieb Andy Shevchenko: >> > > > > > +Cc: some Intel people WRT our internal discussion about similar >> > > > > > problem and solutions. >> > > > > > >> > > > > > On Mon, Jun 8, 2020 at 11:30 AM Lee Jones wrote: >> > > > > > > On Sat, 06 Jun 2020, Michael Walle wrote: >> > > > > > > > Am 2020-06-06 13:46, schrieb Mark Brown: >> > > > > > > > > On Fri, Jun 05, 2020 at 10:07:36PM +0200, Michael Walle wrote: >> > > > > > > > > > Am 2020-06-05 12:50, schrieb Mark Brown: >> > > > > > >> > > > > > ... >> > > > > > >> > > > > > > Right. I'm suggesting a means to extrapolate complex shared and >> > > > > > > sometimes intertwined batches of register sets to be consumed by >> > > > > > > multiple (sub-)devices spanning different subsystems. >> > > > > > > >> > > > > > > Actually scrap that. The most common case I see is a single Regmap >> > > > > > > covering all child-devices. >> > > > > > >> > > > > > Yes, because often we need a synchronization across the entire address >> > > > > > space of the (parent) device in question. >> > > > > > >> > > > > > > It would be great if there was a way in >> > > > > > > which we could make an assumption that the entire register address >> > > > > > > space for a 'tagged' (MFD) device is to be shared (via Regmap) between >> > > > > > > each of the devices described by its child-nodes. Probably by picking >> > > > > > > up on the 'simple-mfd' compatible string in the first instance. >> > > > > > > >> > > > > > > Rob, is the above something you would contemplate? >> > > > > > > >> > > > > > > Michael, do your register addresses overlap i.e. are they intermingled >> > > > > > > with one another? Do multiple child devices need access to the same >> > > > > > > registers i.e. are they shared? >> > > > > >> > > > > No they don't overlap, expect for maybe the version register, which is >> > > > > just there once and not per function block. >> > > > >> > > > Then what's stopping you having each device Regmap their own space? >> > > >> > > Because its just one I2C device, AFAIK thats not possible, right? >> > >> > Not sure what (if any) the restrictions are. >> >> You can only have one device per I2C address. Therefore, I need one >> device >> which is enumerated by the I2C bus, which then enumerates its >> sub-devices. >> I thought this was one of the use cases for MFD. (Regardless of how a >> sub-device access its registers). So even in the "simple-regmap" case >> this >> would need to be an i2c device. Here (see below) >> >> E.g. >> >> &i2cbus { >> mfd-device@10 { >> compatible = "simple-regmap", "simple-mfd"; >> reg = <10>; >> regmap,reg-bits = <8>; >> regmap,val-bits = <8>; >> sub-device@0 { >> compatible = "vendor,sub-device0"; >> reg = <0>; >> }; >> ... >> }; >> >> Or if you just want the regmap: >> >> &soc { >> regmap: regmap@fff0000 { >> compatible = "simple-regmap"; >> reg = <0xfff0000>; >> regmap,reg-bits = <16>; >> regmap,val-bits = <32>; >> }; >> >> enet-which-needs-syscon-too@1000000 { >> vendor,ctrl-regmap = <®map>; >> }; >> }; >> >> Similar to the current syscon (which is MMIO only..). > > We do not need a 'simple-regmap' solution for your use-case. > > Since your device's registers are segregated, just split up the > register map and allocate each sub-device with it's own slice. I don't get it, could you make a device tree example for my use-case? (see also above) -michael > >> > I can't think of any reasons why not, off the top of my head. >> > >> > Does Regmap only deal with shared accesses from multiple devices >> > accessing a single register map, or can it also handle multiple >> > devices communicating over a single I2C channel? >> > >> > One for Mark perhaps. -- -michael