From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755855AbbCXRHd (ORCPT ); Tue, 24 Mar 2015 13:07:33 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:59293 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753289AbbCXRH0 (ORCPT ); Tue, 24 Mar 2015 13:07:26 -0400 Date: Tue, 24 Mar 2015 10:07:52 -0700 From: Mark Brown To: Markus Pargmann Cc: Liam Girdwood , Wolfram Sang , kernel@pengutronix.de, linux-kernel@vger.kernel.org Message-ID: <20150324170752.GQ17265@sirena.org.uk> References: <1427198883-6577-1-git-send-email-mpa@pengutronix.de> <1427198883-6577-2-git-send-email-mpa@pengutronix.de> <20150324160857.GF17265@sirena.org.uk> <20150324164011.GL28604@pengutronix.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="9+VnUxDxRuy97YQ+" Content-Disposition: inline In-Reply-To: <20150324164011.GL28604@pengutronix.de> X-Cookie: A good memory does not equal pale ink. User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: 12.104.145.3 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH 2/2] regulator: max8660: Add error message for missing regulator data 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 --9+VnUxDxRuy97YQ+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Mar 24, 2015 at 05:40:11PM +0100, Markus Pargmann wrote: > On Tue, Mar 24, 2015 at 09:08:57AM -0700, Mark Brown wrote: > > Why is the platform data mandatory? In general the goal is that a > > regulator driver should be able to probe with no platform data. > subdevs[]->platform_data is a struct regulator_init_data which has to > exist so we can register the regulator later. No, that's not the case. The regulator API does not require that one be provided in order to support the above use case. --9+VnUxDxRuy97YQ+ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVEZnnAAoJECTWi3JdVIfQsh8H/2O9qBp+HJmGcYg+x6ohgbBR rw8gSK3UaGx4sNBAVSAH5wtC46vYkXO0bIDAbT1c9kwLpGddmW/bZa8oz6iELaPF FsBDoZSn4k0nxSPHA1xrRmP5NA276If+NJnHtr0eEfs8GOVkNDs4Td9J1MRdjs5k v50lHpxWOIXanm6CAPCgi6aqExxnmCBXJxtbInDmNvHbCwRanj5NNc3dQ8aGTDdL cwenW7IlMdFjxa/LwCIfWHUjl1wOYTTgwGo2k5ftWHARxzVR86V25yyXeq3X+ZCR RjdfU98uHRqOsMqJAmii5Z30L16NbOAOexcHQHubmtf/9tTEDjFiRecHS8MfnLM= =dOvE -----END PGP SIGNATURE----- --9+VnUxDxRuy97YQ+--