From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756139AbbHYUMj (ORCPT ); Tue, 25 Aug 2015 16:12:39 -0400 Received: from comal.ext.ti.com ([198.47.26.152]:46800 "EHLO comal.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756049AbbHYUMh (ORCPT ); Tue, 25 Aug 2015 16:12:37 -0400 Message-ID: <55DCCC35.9060305@ti.com> Date: Tue, 25 Aug 2015 16:12:37 -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: CC: "Kwok, WingMan" , Subject: Re: Using firmware interface to write configuration blob to MMR space References: <55DCB985.10700@ti.com> In-Reply-To: <55DCB985.10700@ti.com> 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 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. > -- Murali Karicheri Linux Kernel, Keystone