Messages in this thread | | | Subject | Re: Using firmware interface to write configuration blob to MMR space | From | Ben Hutchings <> | Date | Tue, 25 Aug 2015 23:57:46 +0100 |
| |
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 Hutchings If you seem to know what you are doing, you'll be given more to do.
[unhandled content-type:application/pgp-signature] | |