From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932711AbbHZOcG (ORCPT ); Wed, 26 Aug 2015 10:32:06 -0400 Received: from bear.ext.ti.com ([192.94.94.41]:49589 "EHLO bear.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751812AbbHZOcE (ORCPT ); Wed, 26 Aug 2015 10:32:04 -0400 Message-ID: <55DDCDCC.2070600@ti.com> Date: Wed, 26 Aug 2015 10:31:40 -0400 From: Murali Karicheri Organization: Texas Instruments User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Ben Hutchings , CC: "Kwok, WingMan" , Subject: Re: Using firmware interface to write configuration blob to MMR space References: <55DCB985.10700@ti.com> <55DCCC35.9060305@ti.com> <1440543466.26026.5.camel@decadent.org.uk> In-Reply-To: <1440543466.26026.5.camel@decadent.org.uk> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/25/2015 06:57 PM, Ben Hutchings wrote: > On Tue, 2015-08-25 at 16:12 -0400, Murali Karicheri wrote: >> On 08/25/2015 02:52 PM, Murali Karicheri wrote: >>> All, >>> >>> 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 to >>> be written to the MMR space to customize the hardware. The vendor is not >>> 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. > Ben, Thanks for your quick response. Ok, we will use request_firmware() in this case. Thanks -- Murali Karicheri Linux Kernel, Keystone