linux-toradex.git/include/linux, branch Apalis_iMX6_LinuxImageV2.6Beta1_20160331

rn5t567: add PMIC driver

2016-03-08T15:15:11+00:00

This adds support for Ricoh RN5T567 PMIC used on Colibri iMX7. The
driver should get unified with rn5t618 driver.

Signed-off-by: Max Krummenacher 
Signed-off-by: Stefan Agner

mfd: Add Ricoh RN5T618 PMIC core driver

2016-03-08T15:15:09+00:00

Ricoh RN5T618 is a power management IC which integrates 3 step-down
DCDC converters, 7 low-dropout regulators, a Li-ion battery charger,
fuel gauge, ADC, GPIOs and a watchdog timer.

This commit adds a MFD core driver to support the I2C communication
with the device.

Signed-off-by: Beniamino Galvani 
Signed-off-by: Lee Jones 
(cherry picked from commit 9bb9e29c78f8d8ee310987fd58a2b908a4ce0c40)

fbcon: logo: allow easy integration of a custom Linux boot logo

2015-12-26T13:48:14+00:00

This patch allows for easy integration of a custom Linux boot logo to
replace the Tux' being shown by default.

Use gimp or the like to create a raw PPM in your desired resolution.

Reduce the number of colours in the image to 224:

  user@host:~$ ppmquant 224 Toradex-640x480.ppm > \
    Toradex-640x480-224.ppm
  ppmquant: making histogram...
  ppmquant: 370 colors found
  ppmquant: choosing 224 colors...
  ppmquant: mapping image to new colors...

Convert it from raw PPM to ASCII format:

  user@host:~$ pnmnoraw Toradex-640x480-224.ppm > \
    Toradex-640x480-ascii-224.ppm

Copy it into the Linux sources:

  cp Toradex-640x480-ascii-224.ppm linux-toradex/drivers/video/logo/\
    logo_custom_clut224.ppm

Activate exclusively custom Linux logo in the kernel configuration:

  Device Drivers -> Graphics support -> Bootup logo ->
    Custom 224-color Linux logo

And re-compile the kernel.

(cherry picked from commit fa2371bff9ac03581881849d8f95678ef3992719)
(cherry picked from commit 481ced9057f340a80bf23775a55a9b657c49201f)

usb: chipidea: use extcon framework for ID and VBUS detection

2015-12-26T13:48:13+00:00

Rather than relying on special USB/PHY pins/registers use the generic
extcon framework with its extcon-usb-gpio implementation to detect ID
and VBUS changes.

(cherry picked from commit a257098741b441e6e84ffe97b7793c580642d502)

extcon: Add resource-managed extcon register function

2015-12-26T13:44:23+00:00

Add resource-managed extcon device register function for convenience.
For example, if a extcon device is attached with new
devm_extcon_dev_register(), that extcon device is automatically
unregistered on driver detach.

Signed-off-by: Sangjung Woo 
[Fix bug about devm_extcon_dev_match/release() and code clean by Chanwoo Choi]
Signed-off-by: Chanwoo Choi 

(cherry picked from commit 1111244ff4493448c0ee66e814e20c6e81d3b93d)

gpio: add parameter to allow the use named gpios

2015-12-26T13:44:22+00:00

The gpio binding document says that new code should always use named
gpios. Patch 40b73183 added support to parse a list of gpios from child
nodes, but does not make it possible to use named gpios. This patch adds
the con_id property and implements it is done in gpiolib.c, where the
old-style of using unnamed gpios still works.

Signed-off-by: Olliver Schinagl 
Acked-by: Bryan Wu 
Acked-by: Dmitry Torokhov 
Reviewed-by: Alexandre Courbot 
Signed-off-by: Linus Walleij 
(cherry picked from commit 1feb57a245a4910b03202a814ffc51a900bd4aca)

of: Make device nodes kobjects so they show up in sysfs

2015-12-26T13:44:22+00:00

Device tree nodes are already treated as objects, and we already want to
expose them to userspace which is done using the /proc filesystem today.
Right now the kernel has to do a lot of work to keep the /proc view in
sync with the in-kernel representation. If device_nodes are switched to
be kobjects then the device tree code can be a whole lot simpler. It
also turns out that switching to using /sysfs from /proc results in
smaller code and data size, and the userspace ABI won't change if
/proc/device-tree symlinks to /sys/firmware/devicetree/base.

v7: Add missing sysfs_bin_attr_init()
v6: Add __of_add_property() early init fixes from Pantelis
v5: Rename firmware/ofw to firmware/devicetree
    Fix updating property values in sysfs
v4: Fixed build error on Powerpc
    Fixed handling of dynamic nodes on powerpc
v3: Fixed handling of duplicate attribute and child node names
v2: switch to using sysfs bin_attributes which solve the problem of
    reporting incorrect property size.

Signed-off-by: Grant Likely 
Tested-by: Sascha Hauer 
Cc: Rob Herring 
Cc: Benjamin Herrenschmidt 
Cc: David S. Miller 
Cc: Nathan Fontenot 
Cc: Pantelis Antoniou 
(cherry picked from commit 75b57ecf9d1d1e17d099ab13b8f48e6e038676be)

Driver core: Unified interface for firmware node properties

2015-12-26T13:42:52+00:00

Add new generic routines are provided for retrieving properties from
device description objects in the platform firmware in case there are
no struct device objects for them (either those objects have not been
created yet or they do not exist at all).

The following functions are provided:

fwnode_property_present()
fwnode_property_read_u8()
fwnode_property_read_u16()
fwnode_property_read_u32()
fwnode_property_read_u64()
fwnode_property_read_string()
fwnode_property_read_u8_array()
fwnode_property_read_u16_array()
fwnode_property_read_u32_array()
fwnode_property_read_u64_array()
fwnode_property_read_string_array()

in analogy with the corresponding functions for struct device added
previously.  For all of them, the first argument is a pointer to struct
fwnode_handle (new type) that allows a device description object
(depending on what platform firmware interface is in use) to be
obtained.

Add a new macro device_for_each_child_node() for iterating over the
children of the device description object associated with a given
device and a new function device_get_child_node_count() returning the
number of a given device's child nodes.

The interface covers both ACPI and Device Trees.

Suggested-by: Grant Likely 
Acked-by: Greg Kroah-Hartman 
Acked-by: Grant Likely 
Signed-off-by: Rafael J. Wysocki 
(cherry picked from commit 8a0662d9ed2968e1186208336a8e1fab3fdfea63)

Driver core: Unified device properties interface for platform firmware

2015-12-26T13:42:51+00:00

Add a uniform interface by which device drivers can request device
properties from the platform firmware by providing a property name
and the corresponding data type.  The purpose of it is to help to
write portable code that won't depend on any particular platform
firmware interface.

The following general helper functions are added:

device_property_present()
device_property_read_u8()
device_property_read_u16()
device_property_read_u32()
device_property_read_u64()
device_property_read_string()
device_property_read_u8_array()
device_property_read_u16_array()
device_property_read_u32_array()
device_property_read_u64_array()
device_property_read_string_array()

The first one allows the caller to check if the given property is
present.  The next 5 of them allow single-valued properties of
various types to be retrieved in a uniform way.  The remaining 5 are
for reading properties with multiple values (arrays of either numbers
or strings).

The interface covers both ACPI and Device Trees.

This change set includes material from Mika Westerberg and Aaron Lu.

Signed-off-by: Aaron Lu 
Signed-off-by: Mika Westerberg 
Acked-by: Greg Kroah-Hartman 
Acked-by: Grant Likely 
Signed-off-by: Rafael J. Wysocki 
(cherry picked from commit b31384fa5de37a100507751dfb5c0a49d06cee67)

leds: leds-gpio: Convert gpio_blink_set() to use GPIO descriptors

2015-12-26T13:42:51+00:00

Commit 21f2aae91e902aad ("leds: leds-gpio: Add support for GPIO
descriptors") already converted most of the driver to use GPIO descriptors.
What is still missing is the platform specific hook gpio_blink_set() and
board files which pass legacy GPIO numbers to this driver in platform data.

In this patch we handle the former and convert gpio_blink_set() to take
GPIO descriptor instead. In order to do this we convert the existing four
users to accept GPIO descriptor and translate it to legacy GPIO number in
the platform code. This effectively "pushes" legacy GPIO number usage from
the driver to platforms.

Also add comment to the remaining block describing that it is legacy code
path and we are getting rid of it eventually.

Suggested-by: Linus Walleij 
Signed-off-by: Mika Westerberg 
Acked-by: Andrew Lunn 
Reviewed-by: Linus Walleij 
Acked-by: Alexandre Courbot 
Signed-off-by: Rafael J. Wysocki 
(cherry picked from commit c673a2b4008103525a3cf21bedf15ffac37bfef0)