Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752610AbdGEJId (ORCPT ); Wed, 5 Jul 2017 05:08:33 -0400 Received: from metis.ext.4.pengutronix.de ([92.198.50.35]:42111 "EHLO metis.ext.4.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752418AbdGEJIb (ORCPT ); Wed, 5 Jul 2017 05:08:31 -0400 Date: Wed, 5 Jul 2017 11:08:29 +0200 From: Michael Grzeschik To: Mark Brown Cc: linux-kernel@vger.kernel.org, kernel@pengutronix.de, Philipp Zabel Subject: Re: [PATCH v2] regmap: irq: allow different device for irq chip and regmap Message-ID: <20170705090829.gy36qcvsovtlnzx4@pengutronix.de> References: <20170622110320.31926-1-m.grzeschik@pengutronix.de> <20170623120043.jgu4i3zbdfraulhc@sirena.org.uk> <20170630133327.bqjzrt5hecjss725@pengutronix.de> <20170704104449.33esknbnloog2c3m@sirena.org.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="263r5z44axvd6jmr" Content-Disposition: inline In-Reply-To: <20170704104449.33esknbnloog2c3m@sirena.org.uk> X-Sent-From: Pengutronix Hildesheim X-URL: http://www.pengutronix.de/ X-IRC: #ptxdist @freenode X-Accept-Language: de,en X-Accept-Content-Type: text/plain X-Uptime: 11:02:47 up 15 days, 19:50, 19 users, load average: 0.05, 0.04, 0.01 User-Agent: NeoMutt/20170113 (1.7.2) X-SA-Exim-Connect-IP: 2001:67c:670:100:5054:ff:fe2a:3aa X-SA-Exim-Mail-From: mgr@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2446 Lines: 57 --263r5z44axvd6jmr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 04, 2017 at 11:44:49AM +0100, Mark Brown wrote: > On Fri, Jun 30, 2017 at 03:33:27PM +0200, Michael Grzeschik wrote: > > On Fri, Jun 23, 2017 at 01:00:43PM +0100, Mark Brown wrote: >=20 > > > syscon is one potential thing here but it seems odd for the sort of > > > hardware that syscon handles to be a good fit for regmap-irq. >=20 > > We have the special case that we use the syscon as the basic driver > > underneath some subdevices that vary in function. We have six arcnet > > controllers sitting side by side in an 8 byte offset. And after them we > > have the next small memory windows for an reset controller and one > > interrupt controller which the other devices reference. >=20 > Why is this a syscon and not a MFD? It sounds exactly like a MFD to me, > syscon is more for cases where things are really jumbled together (even > in single registers) but that sounds like a bunch of separate register > ranges for separate devices that happen to be very close together in > address. You are right. I will rewrite it to MFD. Thanks, Michael --=20 Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | --263r5z44axvd6jmr Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEElXvEUs6VPX6mDPT8C+njFXoeLGQFAllcrIkACgkQC+njFXoe LGSKkw/+NMO9QpjNkjrzSS03jhJGgScIl/MgonOLinL5LA85Gf4sTfARAaV5iody SEW26MfGMI5bhg4ZUbBCzRuhoR7wgZv7a5cJfzq9K7cUwUl6lpbqcE6/KNayMPbQ poSnofLJ2sXfnaug+ewnyLm1aZrZLQXSoXVOy6ZZua7E3nnpBrEtp/VDe5VlQ4hj 3CixImHIH8dehRXsQaOCjsV31NE89MYEPsUEQHlMuP1CyMb09lO0pZ71hnawcVsc VPubYza4Chwfj6ZtyzL8lkkDvihnGh6wwaMvFQMLfb09wuwC4TBPla04mscHEpnN eSTcaQniPP9KF72n6o8yMTCxKC30Djih5xop3JKDeIS0A2R3DCKvZ1cy6lTbrQpi RmRHjkCGiit/XQXS7KqlOC0XMVTs1imZOPsEBAJxAss/Mj78C+BMAt2/M3ZlQk28 HU2sHKW0ZjH76Lj0EbKArH8mWIQ2BoZA+g78XF8Zz8wpuYU+oUuagjr+UTk0i1NT MwuPygwrOqMODdwalGKrbJ8qNw3ZEwkzqaqR/FZI4W4YB4O8B3TSXWwaG2ePHUtc L1zOELHLCvZATY3OSRA131estar7+KwFwwqPzPGHL/v/2vqdAmsoMh4baPpLKjUB 1spiHOTgk2lrZebKFpKQDoMv0RwPggflZDZuFSzK1r/M+JEQ1lQ= =GKNO -----END PGP SIGNATURE----- --263r5z44axvd6jmr--