From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756168AbbHYW6C (ORCPT ); Tue, 25 Aug 2015 18:58:02 -0400 Received: from shadbolt.e.decadent.org.uk ([88.96.1.126]:52917 "EHLO shadbolt.e.decadent.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755822AbbHYW6A (ORCPT ); Tue, 25 Aug 2015 18:58:00 -0400 Message-ID: <1440543466.26026.5.camel@decadent.org.uk> Subject: Re: Using firmware interface to write configuration blob to MMR space From: Ben Hutchings To: Murali Karicheri , linux-firmware@kernel.org Cc: "Kwok, WingMan" , linux-kernel@vger.kernel.org Date: Tue, 25 Aug 2015 23:57:46 +0100 In-Reply-To: <55DCCC35.9060305@ti.com> References: <55DCB985.10700@ti.com> <55DCCC35.9060305@ti.com> Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-+b6qTxeoag6hOtoXnENJ" X-Mailer: Evolution 3.16.3-1 Mime-Version: 1.0 X-SA-Exim-Connect-IP: 31.55.40.54 X-SA-Exim-Mail-From: ben@decadent.org.uk X-SA-Exim-Scanned: No (on shadbolt.decadent.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --=-+b6qTxeoag6hOtoXnENJ Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 2015-08-25 at 16:12 -0400, Murali Karicheri wrote: > On 08/25/2015 02:52 PM, Murali Karicheri wrote: > > All, > >=20 > > One of our SoC integrates a hardware block from a hardware vendor. The > > vendor has provided a configuration blob that is used to customize the > > hardware block for a specific application. This configuration blob is t= o > > be written to the MMR space to customize the hardware. The vendor is no= t > > willing to provide details of the registers. So I am wondering if I > > could use the firmware API (request_firmware) to copy the blob to the > > kernel space so that driver could write these values to the MMR space. > > Is this an acceptable way of using the firmware interface? My research > > so far doesn't see the interface used this way and looking for your > > expert opinion. I think this would be an entirely reasonable use of request_firmware(). Ben. --=20 Ben Hutchings If you seem to know what you are doing, you'll be given more to do. --=-+b6qTxeoag6hOtoXnENJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIVAwUAVdzy6ue/yOyVhhEJAQp70g/9HL7qFE4gZbs0aOkhC7lZNlcIxyPR1pQo qb0xdR1ZlYowOVwoLEEiSzlsCh/cKydvvwjSnpzREj+T3pUxHHKrJwbJCorGuLt/ v1u5nlxaFexMgErTre/TRk/UOyzob4TMsP9dR8Wl6IQuRVwzlFZ6Lz6FJHbBJ5Ny v4RpKI4wblJu0lAE8cEcy3xi1VWrVPMi6WphBOZDh3ylvUZVAaVJSDAWqpOURYUi C5971BAFZ2sjG5V2t7ptt3Y3uGe9M5gG82U/bq7VdDLRjfpQAxsLP/3i+ZDMM8KY bop0EHMzWHgVHeSpwoz9Kp2XhMBZdpWviexQvWkAvJkLVQ77ALchiMhOWRftcO/j jJA9xM8/FHnembVW8Eh4ITwodYkSJutI9WlVkKiu7YhswNHzIieeoOp0f8/4XrkF c69U1OwINQ3VmwL7j8OmM2MBRNXygFyGkty2Y/UiRFG+gBv2U4nL+omMKgHce3fy fOarVyFXqne/uPTcqbj72ViCr7ISnnJ+3RHMa7ewcrgEBnocBbqsrP871gSZ7U2N Pta592v1CSz9A9y+1+dbMYzDVW9J9ltNHENb5v9CQrP+qVmt0225R+wZtMCSrs9s M9XzlYztMoi5aeaIMzEMRu8Fyi/D1Hq4J5dGVSeQFG/y6Fw4vL63jVMKDKB2HUau +7yD5AtT4T4= =4I0B -----END PGP SIGNATURE----- --=-+b6qTxeoag6hOtoXnENJ--