Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp5809430rwb; Mon, 5 Dec 2022 04:32:40 -0800 (PST) X-Google-Smtp-Source: AA0mqf5lr1UfxIGDXAmH9IFK/48zPUFwCKMOH/sFG6XIH8zcGioLh1j+yk7rC7EUS/Euajz9ZcOY X-Received: by 2002:a05:6402:240b:b0:469:9667:704c with SMTP id t11-20020a056402240b00b004699667704cmr60416546eda.318.1670243560077; Mon, 05 Dec 2022 04:32:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1670243560; cv=none; d=google.com; s=arc-20160816; b=Yl//5U5KKgZ9JJCGNfgWuo+5q8WPSlWzOYgL3BBvQyLBu8YP9AlLXnMyO0Nr7kp1D6 E5MyC6b3mZWPcI7CCeV7/pSlZK1e2jpC4lxAH5qCjMxVLFT1CLn6ILP47YZRzekln1yn u5C5Tk76EvIBomHdsmIpsSloH/nXsQafCVHczFV5hC7U1LqvhNNMMCbzR2De+SN29lhB mRGgHfYgF4uif+B2eKmu+Nn/tSYhr0qV/shniSX/sT8tsxJL0w88wPuRnjWDB63Ms3Fe CWtnpy6nKhZgL1XpVp1mC+6U9NrQT2GKt7uX19GoiN3HrvGHJ/PPhsm3HdGT8Dhryyr4 9TAA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=gL7qFyTfdNqY5KxUrXvD9HL/86fdibU+fN6X3H4wNqI=; b=QZQYI60w+AElOnHJrLBkVT6Qggr4GqumdEtOJd8+KpE/xUzf4dHsACaN+PvmEfdzfP 52jeakwqMoQlv0EeWnagAGOLnjHEV4PAgWP481hKo/SR/G0TIcQY94CQWMIZNzCPg96x hkp4dJcmdkx9iz0pJ/At/sgmXYuNEHbFbIrdCh9zXQV8/xAe8j9YsiV18+5R0jWwDlDT 3Jwk8aRkzxONyfHLnWKyaTs4b61ffH8/+tl1fbrwcTip4MVIEzCbe7d35Z2tca6pTzLY C49CcftwYzsa6fdLsu4BVM+Desv/hDfytgNbDCVzq4CNKYmixbFOB0+G0UTMN7w2NBq4 vfsA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=KUW5ObfB; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id t6-20020a056402524600b0046cf113b9c0si507247edd.550.2022.12.05.04.32.18; Mon, 05 Dec 2022 04:32:40 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=KUW5ObfB; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230405AbiLEMF1 (ORCPT + 83 others); Mon, 5 Dec 2022 07:05:27 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43310 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229970AbiLEMF0 (ORCPT ); Mon, 5 Dec 2022 07:05:26 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ACC96C76A; Mon, 5 Dec 2022 04:05:24 -0800 (PST) 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 ams.source.kernel.org (Postfix) with ESMTPS id 2B4C7B80EDA; Mon, 5 Dec 2022 12:05:23 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6BA28C433D7; Mon, 5 Dec 2022 12:05:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1670241921; bh=Sg7hSBYis/7NJ7gp8kAsTusDuRcfqiLMNUytPo5WSiY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=KUW5ObfBGL1ygvaNqOREvi1HSGTyVkGDXPfihbiOoVJkEnAODHZQfvECnAtTB/C9A 4MG3Owee35IONtxBdoClACL5KoFCQ28cdlYd6JhUEygbi/OrlU6/40iSz4nz1W1Ml/ 3rNCpFoLJM74d1PngmDU7bvFmlKpInpTAu/VIczOjym3ep6Nw0o4ahfRiECRVY7OiT p3QoxwnTiZByzTbfa43cr6AgdsZ73JrfUYZAU0OKM7ZxFE5qE52b1QkoC+mtlRs1Le 9CcY+5NqKjPqeUHTntKGfAj81lSS/cBBtXfP1YZc5ztLl29782gAnwgoVvTeHo7g2v aNpE5HvA+cCRA== Date: Mon, 5 Dec 2022 12:05:14 +0000 From: Mark Brown To: Ilpo =?iso-8859-1?Q?J=E4rvinen?= Cc: Xu Yilun , linux-fpga@vger.kernel.org, Wu Hao , Tom Rix , Moritz Fischer , Lee Jones , Matthew Gerlach , Russ Weight , Tianfei zhang , Greg KH , Marco Pagani , LKML Subject: Re: [PATCH v3 7/9] mfd: intel-m10-bmc: Add PMCI driver Message-ID: References: <20221202100841.4741-1-ilpo.jarvinen@linux.intel.com> <20221202100841.4741-8-ilpo.jarvinen@linux.intel.com> <855d463e-fb84-1910-f53-58e6b0a633a4@linux.intel.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="eKKE6fgqZADZWzdx" Content-Disposition: inline In-Reply-To: <855d463e-fb84-1910-f53-58e6b0a633a4@linux.intel.com> X-Cookie: If it ain't broke, don't fix it. X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --eKKE6fgqZADZWzdx Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 05, 2022 at 11:51:15AM +0200, Ilpo J=E4rvinen wrote: > On Sat, 3 Dec 2022, Xu Yilun wrote: > > On 2022-12-02 at 12:08:39 +0200, Ilpo J=E4rvinen wrote: > > > +struct regmap *__devm_m10_regmap_indirect(struct device *dev, > > We name the file intel-m10-bmc-pmci-xxx.c, and this function > > xx_m10_regmap_xx(). But I can see the implementation is just about the = indirect > > bus which from your commit message could be used by various DFL features > > like HSSI or PMCI. So is it better we put the implementation in > > drivers/fpga and name the file dfl-indirect-regmap.c and the > > initialization function dfl_indirect_regmap_init()? > I guess that would be doable unless Mark objects. My understanding was=20 > that he preferred to have in the driver that is currently using it. > Mark, any opinion on this? The above does not look good. As I have said several times now drivers implementing their own regmap operations should use the reg_read() and reg_write() operations in regmap_config when allocating their regmap unless they're doing something unusual. There are a few cases where it makes sense but nothing I've seen here makes it look like this is one of them. Most of the current users don't fit. Please, just implement a normal driver using a normal regmap_config as I've repeatedly said you should if you don't want to provide something generic. --eKKE6fgqZADZWzdx Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmON3nkACgkQJNaLcl1U h9Co7Qf/eIz7h6ibggGjkJrx3WaPVwE60Kkxjo2FsG52Nc0CbeV9PYzJZD4Y8cTd j2GO5Y0k91Sq+K01GdWIUXoBuU6j9cj5PVTh7oSMTLoE9VRgyDKzz8E44heZRdI/ N1mGPiAykoqoiftA7oD//33t4klMzLdp2Rylg+uFRzOi+U+qdSOHMrAheUQ9U0oh miqElD3SlnJCbEIuhP3l0PYmQ0nTi/+GlXIbQWp6LSZeDCpdlQxnDgi/8ObLp4KT efZMN6bdv68UcWpNQdbXiwZru1jOs5IGg60MES8gTpQWM4PxVv/uEE1rvAmL9dCp jcmtWY37whnNfjf5vUGq4IPMMTy5vw== =CtcO -----END PGP SIGNATURE----- --eKKE6fgqZADZWzdx--