[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <557FF50C.10809@rock-chips.com>
Date: Tue, 16 Jun 2015 18:06:04 +0800
From: Caesar Wang <wxt@...k-chips.com>
To: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Stefan Wahren <stefan.wahren@...e.com>
CC: heiko@...ech.de, mark.rutland@....com, devicetree@...r.kernel.org,
linux@....linux.org.uk, pawel.moll@....com,
ijc+devicetree@...lion.org.uk, linus.walleij@...aro.org,
linux-kernel@...r.kernel.org, linux-rockchip@...ts.infradead.org,
robh+dt@...nel.org, galak@...eaurora.org, matthias.bgg@...il.com,
jay.xu@...k-chips.com, linux-arm-kernel@...ts.infradead.org,
Maxime Ripard <maxime.ripard@...e-electrons.com>
Subject: Re: [PATCH v2 0/3] Add the efuse driver on rockchip platform
Hi Srinivas,
在 2015年06月16日 17:21, Srinivas Kandagatla 写道:
> Hi Stefan,
>
>
> On 16/06/15 09:52, Stefan Wahren wrote:
>> Hi Caesar,
>>
>> [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:
>>> 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.
Okay,
I will do that...
Doing.....
203d56b WIP: nvmem: add device tree helper functions
7d822d7 nvmem: sunxi: Move the SID driver to the nvmem framework
f54130d nvmem: qfprom: Add bindings for qfprom
6e078d2 nvmem: qfprom: Add Qualcomm QFPROM support.
750d32b nvmem: Add simple nvmem-mmio consumer helper functions.
6390111 nvmem: Add bindings for simple nvmem framework
1c02217 nvmem: Add nvmem_device based consumer apis.
61ce74f nvmem: Add a simple NVMEM framework for consumers
0f82237 nvmem: Add a simple NVMEM framework for nvmem providers
7547598 regmap: Introduce regmap_get_reg_stride.
f3bc1c0 regmap: Introduce regmap_get_max_register.
f0b3b70 ARM: rockchip: fix the SMP code style
8a28ee6 ARM: rockchip: ensure CPU to enter WFI/WFE state
609deeb ARM: rockchip: fix the CPU soft reset
2a876e4 ARM: rockchip: restore dapswjdp after suspend
e260818 Linux 4.1-rc4
ab992dc watchdog: Fix merge 'conflict'
....
At the moment, I don't know how to use this framework.
I need some time to dig it, I'm happy if you some reference(driver or
document).
>
> I added two of wrappers on top of v5 at:
> https://git.linaro.org/people/srinivas.kandagatla/linux.git/shortlog/refs/heads/nvmem-dev-v5
>
>
> I think I should request Mark to take the framework.
>
>
>
> --srini
>> Regards
>> Stefan
>>
>>
>
>
>
--
Thanks,
- Caesar
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists