On 8/24/2016 3:52 PM, Paolo Pisati wrote:
On Wed, Aug 17, 2016 at 02:33:40PM -0500, Andy Gross wrote:
On Wed, Aug 17, 2016 at 10:48:43AM +0530, Rajendra Nayak wrote:
Hey Andy,
This is a respin of v2 with some minor fixes pointed out by Rob.
Please pull these in for 4.9
Thanks,
Rajendra
I pulled these in.
Did you try to read the content of the qfprom from userspace?
Hi, no I haven't tried it, I can give it a try tomorrow when I
have access to my board and see whats going wrong, but I did
look at Andys for-next and the defconfig still does not have
either nvmem or qcom-qfprom drivers enabled.
Did you manually enable them? or are you seeing this with the drivers
still disabled?
$ uname -a
Linux dragon410c 4.8.0-rc1+ #6 SMP PREEMPT Wed Aug 24 11:11:02 CEST 2016 aarch64
aarch64 aarch64 GNU/Linux
$ lsmod
Module Size Used by
nvmem_qfprom 16384 0
nvmem_core 24576 1 nvmem_qfprom
$ ls -la /sys/bus/nvmem/devices/
total 0
drwxr-xr-x 2 root root 0 Aug 24 10:17 .
drwxr-xr-x 4 root root 0 Aug 24 10:15 ..
lrwxrwxrwx 1 root root 0 Aug 24 10:17 qfprom0 ->
../../../devices/platform/soc/5c000.qfprom/qfprom0
$ cat /sys/bus/nvmem/devices/qfprom0/nvmem
[spontaneous reboot]
This using agross's for-next tree as of today ("54ba896 Merge branch
'arm64-defconfig-for-4.9' into all-for-4.8") and defconfig.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
