Re: [PATCH v2 0/3] Add the efuse driver on rockchip platform

Hi Srinivas,

Am 16.06.2015 um 12:54 schrieb Srinivas Kandagatla:

On 16/06/15 11:06, Caesar Wang wrote:

quoted

Hi Srinivas,

在 2015年06月16日 17:21, Srinivas Kandagatla 写道:

quoted

Hi Stefan,


On 16/06/15 09:52, Stefan Wahren wrote:

quoted

Hi Caesar,

[add Maxime and Srinivas]

Am 16.06.2015 um 09:27 schrieb Caesar Wang:

quoted

The original driver is uploaded by Jianqun.
Here is his patchs:
     https://patchwork.kernel.org/patch/5410341/
     https://patchwork.kernel.org/patch/5410351/

Jianqun, nevermind!
I check-pick it and re-upload the driver for the upstream.
e.g.:
     Tested by on minnie board.(kernel-4.1-rc8)
     cd /sys/devices/platform/ffb40000.efuse
     localhost ffb40000.efuse # cat cpu_leakage_show
     cpu_version_show
     The results:
             19
             2

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
efuse drivers:

https://lkml.org/lkml/2015/5/21/643

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
mailing list.

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
int *val)
{
    /* efuse specific read sequence */
    ...
}

I will need a specific read sequence too.

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 locking
operations?

In case of a read only driver, is everything handle by devicetree or do
we need an empty write operation?

Best regards
Stefan
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html