Am 16.06.2015 um 12:54 schrieb Srinivas Kandagatla:
On 16/06/15 11:06, Caesar Wang wrote:
å 2015å06æ16æ 17:21, Srinivas Kandagatla åé:
On 16/06/15 09:52, Stefan Wahren wrote:
[add Maxime and Srinivas]
Am 16.06.2015 um 09:27 schrieb Caesar Wang:
The original driver is uploaded by Jianqun.
Here is his patchs:
I check-pick it and re-upload the driver for the upstream.
Tested by on minnie board.(kernel-4.1-rc8)
localhost ffb40000.efuse # cat cpu_leakage_show
Changes in v2:
- Change the document decription.
- Move the efuse driver into driver/soc/vendor.
- update the efuse driver.
- Add the dts node on RK3288.
i want to mention that there is a upcoming new framework suitable for
Unfortunately i don't know the current development state.
Currently this framework is used by atleast 3 drivers(qcom-tsens,
qcom-cpr, begel-bone-cape manager) which are still floating in the
I was hoping that these 3 users would getback with tested-by.. which
did not happen for last 3-4 weeks.
I would appreciate, If you could try framework too, and let me know.
yes i work on OCOTP driver for MXS platform and i will try ...
int rockchip_efuse_reg_read(void *context, unsigned int reg, unsigned
/* efuse specific read sequence */
I will need a specific read sequence too.
We already have that in place.
Sorry for these newbie questions:
What data structure does context points to for this reg_read opteration?
Do we need range checking of reg or is it handled by the framework?
Are there any limitation for reg_read regarding sleeping or lockingThere are no limitaions as such from nvmem framework, regmap might have limitations w.r.t to sleeping and fast_io, as fast_io would take spinlocks, AFAIK the providers would not have fast_io, as they not IO devices.
Yes, if you pass read-only flag in the provider, the framework would not attempt to even write.
In case of a read only driver, is everything handle by devicetree or do
we need an empty write operation?