From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755003AbcAHNhS (ORCPT ); Fri, 8 Jan 2016 08:37:18 -0500 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:41978 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751091AbcAHNhO (ORCPT ); Fri, 8 Jan 2016 08:37:14 -0500 Date: Fri, 8 Jan 2016 13:36:48 +0000 From: Mark Brown To: Laxman Dewangan Cc: Krzysztof Kozlowski , rtc-linux@googlegroups.com, robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com, ijc+devicetree@hellion.org.uk, galak@codeaurora.org, linus.walleij@linaro.org, gnurou@gmail.com, lee.jones@linaro.org, a.zummo@towertech.it, alexandre.belloni@free-electrons.com, lgirdwood@gmail.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org, swarren@nvidia.com, treding@nvidia.com, Chaitanya Bandi Message-ID: <20160108133648.GQ6588@sirena.org.uk> References: <1452177524-23192-1-git-send-email-ldewangan@nvidia.com> <1452177524-23192-6-git-send-email-ldewangan@nvidia.com> <568F8D7E.10500@nvidia.com> <20160108125117.GM6588@sirena.org.uk> <568FB3DD.4090503@nvidia.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="yhCE4sTDB5mqd9YJ" Content-Disposition: inline In-Reply-To: <568FB3DD.4090503@nvidia.com> X-Cookie: APL hackers do it in the quad. User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: 2a01:348:6:8808:fab::3 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [rtc-linux] [PATCH 5/6] rtc: max77620: add support for max77620/max20024 RTC driver X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mezzanine.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --yhCE4sTDB5mqd9YJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Jan 08, 2016 at 06:34:29PM +0530, Laxman Dewangan wrote: > If we get the parent device, regmap handle and interrupt number from mfd > core independent of the PMIC (MAX77620 or MAX77686), then same driver can be > used here. > Two way which I can think of here: Parent device is just dev->parent, you can use dev_get_regmap() to get a regmap given a struct device and you can use platform resources to pass the interrupts to the children from the MFD (there's some examples, wm831x is one). --yhCE4sTDB5mqd9YJ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWj7tvAAoJECTWi3JdVIfQFUYH/iWXnQyflBGLqEOSyhQUyPgp NOq8StSdQ/zEvoKZ7DfFPZ+aRlOXJPG9dQ6PDczj1PSl5xXlgkUAtcHVfPc8aFOp 9c70hUDX74st468a80SlmDQc49LYDH99umpzeJs1akq8l8b9Z9s6gOFNGV79lHXW GJwpG/KtmMe3hApod10gF0SlfArie6DC30xxPa2sQQgBUqrmfA3eoxvSSLuiLcIn X5KVtNUO9/tRYJWN7Jo33S6aqXriMbsvuJxXlttuONFYVUKGMz/uPd493Pt8Za3O 02Lgm6YtKWgKC3zi9lQ6MA13lIqFQT6y3anU3zAATZoSYiHiGjQPeKRdYctfNrQ= =R4fS -----END PGP SIGNATURE----- --yhCE4sTDB5mqd9YJ--