Hilman, Kevin wrote:
Mahaveer, Vishal vish...@ti.com writes:
Hilman, Kevin wrote:
No.
You want it on only
1) if the connectivity chip is present, *and*
2) BT, WLAN, FM or GPS are being used.
The current patch assumes that a connectivity chip is present
whenever the TWL is
Mahaveer, Vishal vish...@ti.com writes:
omap4_clk32kg regulator is used by connectivity (WLAN/BT/GPS) chip on
omap4 platforms.
Set always_on flag to true for connectivity chip to operate.
The driver/init for the connectivity chip should be using the regulator
API to enable/disable the
Hilman, Kevin wrote:
No.
You want it on only
1) if the connectivity chip is present, *and*
2) BT, WLAN, FM or GPS are being used.
The current patch assumes that a connectivity chip is present
whenever the TWL is present, which may be true on the platform you're
currently working on,
Mahaveer, Vishal vish...@ti.com writes:
Hilman, Kevin wrote:
No.
You want it on only
1) if the connectivity chip is present, *and*
2) BT, WLAN, FM or GPS are being used.
The current patch assumes that a connectivity chip is present
whenever the TWL is present, which may be true on
Vishal Mahaveer vish...@ti.com writes:
omap4_clk32kg regulator is used by connectivity (WLAN/BT/GPS) chip on
omap4 platforms.
Set always_on flag to true for connectivity chip to operate.
The driver/init for the connectivity chip should be using the regulator
API to enable/disable the
omap4_clk32kg regulator is used by connectivity (WLAN/BT/GPS) chip on
omap4 platforms.
Set always_on flag to true for connectivity chip to operate.
The driver/init for the connectivity chip should be using the regulator
API to enable/disable the regulator as needed.
The connectivity chip is
