From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932359AbbCCSqS (ORCPT ); Tue, 3 Mar 2015 13:46:18 -0500 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:48379 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932261AbbCCSqR (ORCPT ); Tue, 3 Mar 2015 13:46:17 -0500 Date: Tue, 3 Mar 2015 18:44:03 +0000 From: Mark Brown To: Christophe Leroy Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-spi@vger.kernel.org Message-ID: <20150303184403.GE21293@sirena.org.uk> References: <20150226161142.D08681A2360@localhost.localdomain> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="BPgJ2GbR8X7BKSc9" Content-Disposition: inline In-Reply-To: <20150226161142.D08681A2360@localhost.localdomain> X-Cookie: My LESLIE GORE record is BROKEN ... User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: 94.175.94.161 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH] spi: fsl-spi: use of_iomap() to map parameter ram on CPM1 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 --BPgJ2GbR8X7BKSc9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Feb 26, 2015 at 05:11:42PM +0100, Christophe Leroy wrote: > On CPM2, the SPI parameter RAM is dynamically allocated in the dualport RAM > whereas in CPM1, it is statically allocated to a default address with > capability to relocate it somewhere else via the use of CPM micropatch. > The address of the parameter RAM is given by the boot loader and expected > to be mapped via of_iomap() Why are we using of_iomap() rather than a generic I/O mapping function here? --BPgJ2GbR8X7BKSc9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJU9gDyAAoJECTWi3JdVIfQZeYH/0iTYbCGDUqESLRuSfhDbpdi mPGeWIAHENbJODx9JOsTepCbk3sQ2fdmWq7LCmlv/j412/9LPSk8Y0X7GsC73tE0 vueM2sEm4ZAlo+FbfUg2dx4xqtc9aTj8sX75CkTNL/U4ZAhvc60Q/DK56qmE+JEQ 8D95NxXQxJER2AqSAA/GUOwXpLAM01eRDKFEI6Ap+TOM3pNGeTjCJUxmlf4EJuHR 8Xy9nOUpE8QaMPDFx1hprNZdSXz0xZ5AjrLqgS3tQVE5WxHcc7VdOUQBbQ0L9pLO idvttOchxPldNxLhuBAQki7tyOETNUSOFhPf74x9FrOwGWSeV9cN4jdI9vzzMJ8= =1Xz7 -----END PGP SIGNATURE----- --BPgJ2GbR8X7BKSc9--