linux-toradex.git/drivers/nvmem, branch v4.6-rc6

nvmem: mediatek: Fix later provider initialization

2016-03-05T20:20:29+00:00

Possibly, provider driver initialization is later than
consumer driver. Use function subsys_initcall to initialize
NVMEM provider early to ensure NVMEM consumer doesn't need
to -EPROBE_DEFER.

Signed-off-by: Andrew-CT Chen 
Signed-off-by: Srinivas Kandagatla 
Signed-off-by: Greg Kroah-Hartman

nvmem: imx-ocotp: Fix return value of imx_ocotp_read

2016-03-05T20:20:29+00:00

imx_ocotp_read() should return 0 on success.

Signed-off-by: Axel Lin 
Signed-off-by: Srinivas Kandagatla 
Signed-off-by: Greg Kroah-Hartman

nvmem: Fix dependencies for !HAS_IOMEM archs

2016-03-05T20:20:29+00:00

Not every arch has io memory.
So, unbreak the build by fixing the dependencies.

Signed-off-by: Richard Weinberger 
Signed-off-by: Srinivas Kandagatla 
Signed-off-by: Greg Kroah-Hartman

nvmem: Add backwards compatibility support for older EEPROM drivers.

2016-03-02T00:55:48+00:00

Older drivers made an 'eeprom' file available in the /sys device
directory. Have the NVMEM core provide this to retain backwards
compatibility.

Signed-off-by: Andrew Lunn 
Acked-by: Srinivas Kandagatla 
Signed-off-by: Greg Kroah-Hartman

nvmem: Add flag to export NVMEM to root only

2016-03-02T00:55:48+00:00

Legacy AT24, AT25 EEPROMs are exported in sys so that only root can
read the contents. The EEPROMs may contain sensitive information. Add
a flag so the provide can indicate that NVMEM should also restrict
access to root only.

Signed-off-by: Andrew Lunn 
Acked-by: Srinivas Kandagatla 
Signed-off-by: Greg Kroah-Hartman

Merge 4.5-rc4 into char-misc-next

2016-02-14T22:25:59+00:00

We want those fixes in here as well.

Signed-off-by: Greg Kroah-Hartman

nvmem: core: fix error path in nvmem_add_cells()

2016-02-12T03:23:28+00:00

The current code fails to nvmem_cell_drop(cells[0]) - even worse, if
the loop above fails already at i==0, we'll enter an essentially
infinite loop doing nvmem_cell_drop on cells[-1], cells[-2], ... which
is unlikely to end well.

Also, we're not freeing the temporary backing array cells on the error
path.

Signed-off-by: Rasmus Villemoes 
Signed-off-by: Greg Kroah-Hartman

nvmem: qfprom: Specify LE device endianness

2016-02-08T07:09:13+00:00

The qfprom is a little endian device, but so far we've been
relying on the regmap mmio bus handling this for us without
explicitly stating that fact. After commit 4a98da2164cf
(regmap-mmio: Use native endianness for read/write, 2015-10-29),
the regmap mmio bus will read/write with the __raw_*() IO
accessors, instead of using the readl/writel() APIs that do
proper byte swapping for little endian devices.

So if we're running on a big endian processor and haven't
specified the endianness explicitly in the regmap config or in
DT, we're going to switch from doing little endian byte swapping
to big endian accesses without byte swapping, leading to some
confusing results. Specify the endianness explicitly so that the
regmap core properly byte swaps the accesses for us.

Cc: Rajendra Nayak 
Cc: Kevin Hilman 
Cc: Tyler Baker 
Cc: Simon Arlott 
Cc: Mark Brown 
Signed-off-by: Stephen Boyd 
Signed-off-by: Srinivas Kandagatla 
Signed-off-by: Greg Kroah-Hartman

nvmem: core: return error for non word aligned access

2016-02-08T07:09:13+00:00

nvmem providers have restrictions on register strides, so return error
when users attempt to read/write buffers with sizes which are less
than word size.

Without this patch the userspace would continue to try as it does not
get any error from the nvmem core, resulting in a hang or endless loop
in userspace.

Reported-by: Ariel D'Alessandro 
Signed-off-by: Srinivas Kandagatla 
Signed-off-by: Greg Kroah-Hartman

nvmem: rockchip: trivial: Make the driver more readability

2016-02-08T07:07:21+00:00

1) Make the include file to sort from order
2) clean up the driver to make more readability

Let's clean up such trivial details.

Signed-off-by: Caesar Wang 
Signed-off-by: Srinivas Kandagatla 
Signed-off-by: Greg Kroah-Hartman