Using firmware interface to write configuration blob to MMR space
Quoted 13 lines · Murali Karicheri
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.
Signature · 2 lines
Murali Karicheri Linux Kernel, Keystone
Quoted 13 lines · Murali Karicheri
Quoted 12 lines · Murali Karicheri
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.
Signature · 2 lines
Ben Hutchings If you seem to know what you are doing, you'll be given more to do.
Quoted 15 lines · Ben Hutchings
Quoted 13 lines · Murali Karicheri
Quoted 12 lines · Murali Karicheri
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.
Quoted 4 lines
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
Signature · 2 lines
Murali Karicheri Linux Kernel, Keystone