linux-toradex.git/drivers/pinctrl/pinctrl-tegra20.c, branch v4.2.6

pinctrl: tegra: some bits move between registers

2015-03-09T17:10:58+00:00

Some of the pinmux configuration bits that exist in "drive group"
registers in Tegra30..Tegra124 move to the "pinmux" registers on future
chips. Add a flag to support this.

Signed-off-by: Stephen Warren 
Tested-by: Alexandre Courbot 
Signed-off-by: Linus Walleij

pinctrl: drop owner assignment from platform_drivers

2014-10-20T14:21:21+00:00

A platform_driver does not need to set an owner, it will be populated by the
driver core.

Signed-off-by: Wolfram Sang

pinctrl: Make of_device_id array const

2014-08-29T05:13:04+00:00

Make of_device_id array const, because all OF functions handle it as
const.

Signed-off-by: Kiran Padwal 
Acked-by: Thierry Reding 
Acked-by: Stephen Warren 
Acked-by: Shawn Guo 
Signed-off-by: Linus Walleij

pinctrl: tegra: remove fsafe from data tables

2014-04-22T14:50:24+00:00

The fsafe value in the pingroup data tables is only used to implement
tegra_pinctrl_disable(). The only reason this function is called is when
dynamically switching between pinmux states, i.e. when disabling the old
state before programming the new state. It's simpler to have the new
target state define the expected value of each pin (and all current DTs
do that). This also gives more flexibility, since it allows individual
boards explicit control over the "inactive" mux function for each pin,
rather than requiring it to be an SoC-specific value. Assuming this, we
can get rid of the fsafe value from the driver completely, thus saving
some more space in the driver tables.

While re-writing the content of tegra124_pingroups[], fix the indentation
to use a TAB instead of spaces.

Signed-off-by: Stephen Warren 
Acked-by: Laxman Dewangan 
Signed-off-by: Linus Walleij

pinctrl: tegra: remove redundant data table fields

2014-04-22T14:48:39+00:00

Any SoC which supports the einput, odrain, lock, ioreset, or rcv_sel
options has the relevant HW register fields in the same register as the
mux function selection. Similarly, the drvtype option is always in the
drive register, if it is supported at all. Hence, we don't need to have
struct *_reg fields in the pin group table to define which register and
bank to use for those options. Delete this to save space in the driver's
data tables.

However, many of those options are not supported on all SoCs, or not
supported on some pingroups. We need a way to detect when they are
supported. Previously, this was indicated by setting the struct *_reg
field to -1. With the struct *_reg fields removed, we use the struct
*_bit fields for this purpose instead. The struct *_bit fields need to
be expanded from 5 to 6 bits in order to store a value outside the valid
HW bit range of 0..31.

Even without removing the struct *_reg fields, we still need to add code
to validate the struct *_bit fields, since some struct *_bit fields were
already being set to -1, without an option-specific struct *_reg field to
"guard" them. In other words, before this change, the pinmux driver might
allow some unsupported options to be written to HW.

Signed-off-by: Stephen Warren 
Signed-off-by: Linus Walleij

pinctrl: tegra: dynamically calculate function list of groups

2014-03-12T14:23:41+00:00

The per-SoC data structures for Tegra pinctrl stored some information
in a redundant way. Specifically, the list of groups that each function
could be muxed onto was stored once explicitly, and also as part of the
definition of each group. Eliminate this redundancy, and calculate each
function's list of valid groups at pinctrl probe time. This removes
thousands of lines of code from the pinctrl driver and ~16K from the
vmlinux binary size, and adds only about 500uS to the boot process (on
Tegra30; newer SoCs will likely be faster still).

Signed-off-by: Stephen Warren 
Signed-off-by: Linus Walleij

pinctrl: tegra: init Tegra20/30 at module_init time

2014-03-12T14:22:29+00:00

The Tegra20/30 pinctrl drivers currently initializes at arch_initcall,
whereas Tegra114/124 pinctrl drivers initialize at module_init time.
Convert Tegra20/30 to work the same way as the other drivers.

Signed-off-by: Stephen Warren 
Signed-off-by: Linus Walleij

pinctrl: tegra: add support for rcv-sel and drive type

2013-01-18T15:13:52+00:00

NVIDIA's Tegra114 added two more configuration parameter in pinmux i.e.
rcv-sel and drive type.

rcv-sel: Select between High and Normal VIL/VIH receivers.
	RCVR_SEL=1: High VIL/VIH
	RCVR_SEL=0: Normal VIL/VIH

drv_type: Ouptput drive type:
	33-50 ohm driver: 0x1
	66-100ohm driver: 0x0

Add support of these parameters to be configure from DTS file.

Tegra20 and Tegra30 does not support this configuration and hence initialize their
pinmux structure with reg = -1.

Originally written by Pritesh Raithatha.
Changes by ldewangan:
	- remove drvtype_width as it is always 2.
	- Better describe the change.

Signed-off-by: Pritesh Raithatha 
Signed-off-by: Laxman Dewangan 
Reviewed-by: Stephen Warren 
Signed-off-by: Linus Walleij

Drivers: pinctrl: remove __dev* attributes.

2013-01-03T23:57:02+00:00

CONFIG_HOTPLUG is going away as an option.  As a result, the __dev*
markings need to be removed.

This change removes the use of __devinit, __devexit_p, __devinitdata,
and __devexit from these drivers.

Based on patches originally written by Bill Pemberton, but redone by me
in order to handle some of the coding style issues better, by hand.

Cc: Bill Pemberton 
Cc: Linus Walleij 
Cc: Jean-Christophe Plagniol-Villard 
Cc: Stephen Warren 
Cc: Srinidhi Kasagar 
Cc: Barry Song 
Cc: Viresh Kumar 
Cc: Thomas Petazzoni 
Cc: Jason Cooper 
Cc: Sebastian Hesselbarth 
Cc: Andrew Lunn 
Signed-off-by: Greg Kroah-Hartman

pinctrl: remove use of __devinitdata

2012-11-28T19:55:55+00:00

CONFIG_HOTPLUG is going away as an option so __devinitdata is no
longer needed.

Signed-off-by: Bill Pemberton 
Acked-by: Jean-Christophe PLAGNIOL-VILLARD 
Cc: Viresh Kumar 
Acked-by: Linus Walleij 
Signed-off-by: Greg Kroah-Hartman