linux-stable.git/drivers/power/avs, branch linux-4.3.y

PM / AVS: rockchip-io: add io selectors and supplies for rk3368

2015-08-08T01:07:52+00:00

This adds the necessary data for handling io voltage domains on the rk3368.
As interesting tidbit, the rk3368 contains two separate iodomain areas.
One in the regular General Register Files (GRF) and one in PMUGRF in the
pmu power domain.

Signed-off-by: Heiko Stuebner 
Acked-by: Kevin Hilman 
Signed-off-by: Rafael J. Wysocki

PM / AVS: rockchip-io: depend on CONFIG_POWER_AVS

2015-08-08T01:07:52+00:00

The rockchip io-domain driver currently only depends on ARCH_ROCKCHIP
itself. This makes it possible to select the power-domain driver, but
not the POWER_AVS class and results in the iodomain-driver not getting
build in this case.

So add the additional dependency, which also results in the driver
config option now being placed nicely into the AVS submenu.

Fixes: 662a958638bd ("PM / AVS: rockchip-io: add driver handling Rockchip io domains")
Signed-off-by: Heiko Stuebner 
Acked-by: Kevin Hilman 
Signed-off-by: Rafael J. Wysocki

PM / AVS: rockchip-io: add driver handling Rockchip io domains

2014-09-25T16:57:23+00:00

IO domain voltages on some Rockchip SoCs are variable but need to be
kept in sync between the regulators and the SoC using a special
register.

A specific example using rk3288:
- If the regulator hooked up to a pin like SDMMC0_VDD is 3.3V then
  bit 7 of GRF_IO_VSEL needs to be 0.  If the regulator hooked up to
  that same pin is 1.8V then bit 7 of GRF_IO_VSEL needs to be 1.

Said another way, this driver simply handles keeping bits in the SoC's
general register file (GRF) in sync with the actual value of a voltage
hooked up to the pins.

Note that this driver specifically doesn't include:
- any logic for deciding what voltage we should set regulators to
- any logic for deciding whether regulators (or internal SoC blocks)
  should have power or not have power

If there were some other software that had the smarts of making
decisions about regulators, it would work in conjunction with this
driver.  When that other software adjusted a regulator's voltage then
this driver would handle telling the SoC about it.  A good example is
vqmmc for SD.  In that case the dw_mmc driver simply is told about a
regulator.  It changes the regulator between 3.3V and 1.8V at the
right time.  This driver notices the change and makes sure that the
SoC is on the same page.

Signed-off-by: Heiko Stübner 
Signed-off-by: Doug Anderson 
Reviewed-by: Santosh Shilimkar 
[khilman: fix compiler warnings]
Signed-off-by: Kevin Hilman

PM / AVS: SmartReflex: use devm_* API to initialize SmartReflex

2013-06-10T17:50:48+00:00

Use of of devm_* API for resource allocation provides benefits such
as auto handling of resource free. This reduces possibility have
memory leaks in case of wrong error handling. All direct release
calls should be removed to avoid races.

Reported-by: Grygorii Strashko 
Signed-off-by: Andrii Tseglytskyi 
Signed-off-by: Kevin Hilman

PM / AVS: SmartReflex: use omap_sr * for enable/disable interface

2013-06-10T17:46:18+00:00

SmartReflex driver interface is natively divided to two parts:

- external SmartReflex interface
- interface between SmartReflex driver and SmartReflex Class

Functions which belong to AVS class interface can use
struct omap_sr* instead of struct voltatedomain*, to provide a
direct connection between SR driver and SR class. This allows
us to optimize and not do additional lookups where none is
required.

sr_enable() and sr_disable() are interface functions between
SR driver and SR class. They are typically used by Class driver
to enable/disable SmartReflex hardware module.
Now they take struct omap_sr* as input parameter.

Signed-off-by: Andrii Tseglytskyi 
Acked-by: Nishanth Menon 
Signed-off-by: Kevin Hilman

PM / AVS: SmartReflex: use omap_sr * for minmax interfaces

2013-06-10T17:46:17+00:00

SmartReflex driver interface is natively divided to two parts:

- external SmartReflex interface
- interface between SmartReflex driver and SmartReflex Class

Functions which belong to AVS class interface can use
struct omap_sr* instead of struct voltatedomain*, to provide a
direct connection between SR driver and SR class. This allows
us to optimize and not do additional lookups where none is
required.

sr_configure_minmax() is interface function between SR driver
and SR class. It is typically used by Class driver to
configure MINMAXAVG module inside SmartReflex module.
Now it takes struct omap_sr* as input parameter.

Signed-off-by: Andrii Tseglytskyi 
Acked-by: Nishanth Menon 
Signed-off-by: Kevin Hilman

PM / AVS: SmartReflex: use omap_sr * for errgen interfaces

2013-06-10T17:46:17+00:00

SmartReflex driver interface is natively divided to two parts:

- external SmartReflex interface
- interface between SmartReflex driver and SmartReflex Class

Functions which belong to AVS class interface can use
struct omap_sr* instead of struct voltatedomain*, to provide a
direct connection between SR driver and SR class. This allows
us to optimize and not do additional lookups where none is
required.

sr_disable_errgen() and sr_configure_errgen() are interface
functions between SR driver and SR class. They are typically
used by Class driver to configure error generator module during
SmartReflex enable/disable sequence.
Now they take struct omap_sr* as input parameter.

Signed-off-by: Andrii Tseglytskyi 
Acked-by: Nishanth Menon 
Signed-off-by: Kevin Hilman

PM / AVS: SmartReflex: fix driver name

2013-06-10T17:35:17+00:00

DRIVER_NAME was undefined for SmartReflex. Now it is
defined with valid value "smartreflex". It is needed
to define proper value for:
MODULE_ALIAS("platform:" DRIVER_NAME);

Signed-off-by: Andrii Tseglytskyi 
Acked-by: Nishanth Menon 
Signed-off-by: Kevin Hilman

PM / AVS: SmartReflex: disable runtime PM on driver remove

2013-06-10T17:35:17+00:00

Runtime PM should be disabled for device on driver remove,
otherwise runtime PM will be not balanced, and this will cause
an error message, on next driver probe.

Signed-off-by: Andrii Tseglytskyi 
Acked-by: Nishanth Menon 
Signed-off-by: Kevin Hilman

PM / AVS: SmartReflex: disable errgen before vpbound disable

2013-06-10T17:35:17+00:00

vpboundsintr_en is available inside the IP block as an re-sycned
version and one which is not. Due to this, there is an 1 sysclk
cycle window where the SR_SInterruptz signal could be asserted low.
IF, intr_en is cleared on the exact same cycle as the irqclr, an
additional pulse is generated which indicates for VP that
an additional adjustment of voltage is required.

This results in VP doing two voltage adjustments for the SRERR
(based on configuration, upto 4 steps), instead of the needed
1 step.
Due to the unexpected pulse from AVS which breaks the AVS-VP
communication protocol, VP also ends up in a stuck condition by
entering a state where VP module remains non-responsive
to any futher AVS adjustment events. This creates the symptom
called "TRANXDONE Timeout" scenario.

By disabling errgen prior to disable of intr_en, this situation
can be avoided.

Signed-off-by: Vincent Bour 
Signed-off-by: Leonardo Affortunati 
Signed-off-by: Nishanth Menon 
Signed-off-by: Andrii.Tseglytskyi 
Signed-off-by: Kevin Hilman