Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752451AbdGDKo7 (ORCPT ); Tue, 4 Jul 2017 06:44:59 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:58144 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752276AbdGDKo6 (ORCPT ); Tue, 4 Jul 2017 06:44:58 -0400 Date: Tue, 4 Jul 2017 11:44:49 +0100 From: Mark Brown To: Michael Grzeschik Cc: linux-kernel@vger.kernel.org, kernel@pengutronix.de, Philipp Zabel Message-ID: <20170704104449.33esknbnloog2c3m@sirena.org.uk> References: <20170622110320.31926-1-m.grzeschik@pengutronix.de> <20170623120043.jgu4i3zbdfraulhc@sirena.org.uk> <20170630133327.bqjzrt5hecjss725@pengutronix.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="huou73jb2decq5bl" Content-Disposition: inline In-Reply-To: <20170630133327.bqjzrt5hecjss725@pengutronix.de> X-Cookie: I feel ... JUGULAR ... User-Agent: NeoMutt/20170306 (1.8.0) X-SA-Exim-Connect-IP: 2001:470:1f1d:6b5::3 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH v2] regmap: irq: allow different device for irq chip and regmap X-SA-Exim-Version: 4.2.1 (built Tue, 02 Aug 2016 21:08:31 +0000) X-SA-Exim-Scanned: No (on mezzanine.sirena.org.uk); Unknown failure Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1591 Lines: 39 --huou73jb2decq5bl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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: > > 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. > 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. 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. --huou73jb2decq5bl Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAllbcaAACgkQJNaLcl1U h9BaMwf+Od/nVSV9l6Y8Jmj3HLIpUi4AnIfEiMqKYbsi4gEBP3uVbvQhxJUHGWkt 9CZAIpTC/H57S00FZTQbeXGgHXLtyU6hH7r2zuuOyyGJK1qMFQj1GwT2e8Q3xxsX Wz9ZLuWmukD4I60hwVG637cvbOtfVPD01pabmyCORqU2gXeQRcB0VDasMYs/DoYq Y3dObxuFzdyJQpMz5/210EXGjarYiJrxIv6VUwFAnzLhFXXWK1/hZre0tDQmDHzN cg62bt25PMai71b/RTQhDxSwniH2a+HhKJphukDK6au6Wipa0GU2pnDmWI7T4BFm yiHNt+urRkyU5G8of45Fd6+IP1QIFg== =zBit -----END PGP SIGNATURE----- --huou73jb2decq5bl--