Hi,
On Fri, Feb 14, 2014 at 08:44:31AM -0800, Tony Lindgren wrote:
> The following changes since commit 38dbfb59d1175ef458d006556061adeaa8751b72:
>
> Linus 3.14-rc1 (2014-02-02 16:42:13 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmli
Add documentation for device tree description for basic voltage domain
for Texas Instruments OMAP compatible SoC family of processors which
controls both bias and supply voltage planes.
Signed-off-by: Nishanth Menon
---
.../bindings/power/voltdm/voltdm_omap.txt | 24 ++
From: Mike Turquette
This patch provides helper functions for drivers that wish to scale
voltage through the clock rate-change notifiers. The approach taken
is that the user-driver(cpufreq/devfreq) do not care about the
details of the OPP table, nor does it care about handling the voltage
regulat
Hi,
On many SoCs such as OMAP, hardware blocks are isolated into voltage
domains allowing for individual tweaks for optimal power-performance
tradeoffs. Frameworks such as cpufreq, devfreq provide a top level
control of these hardware blocks. Most SoCs have different knobs to
fine tune the voltage
Add documentation for voltage domain binding format. Specific
voltage domains will have bindings corresponding to them.
Signed-off-by: Nishanth Menon
---
.../bindings/power/voltdm/voltage_domain.txt | 65
1 file changed, 65 insertions(+)
create mode 100644
Document
Many SoCs have basic concepts of voltage rails supplying a specific
SoC device. These voltage rails may be as simple as a single regulator
or complex to be three or more regulators that are transitioned in
tandem with respect to clock changes. In some cases, they may tend
to use custom frameworks t
From: Mike Turquette
Removes directly handling of OPP tables and voltage regulators by
calling of_clk_cpufreq_notifier_handler, introduced by commit "clk:
cpufreq helper for voltage scaling".
In the future this can help consolidate code found across similar
CPUfreq drivers.
[n...@ti.com: update
OMAP platforms have multiple voltage domains, but each with consistent
behavior of controlling the VDD (supply) and VBB(ABB/Bias voltage).
These need to be sequenced in a specific order for functionality.
Further optimization such as AVS(Adaptive Voltage Scaling), optimized
voltages from efuse(Cla
Hi,
On Tue, Feb 18, 2014 at 09:30:21AM -0800, Greg KH wrote:
> > > > > +static int dsps_musb_dbg_init(struct musb *musb, struct dsps_glue
> > > > > *glue)
> > > > > +{
> > > > > + struct dentry *root;
> > > > > + struct dentry *file;
> > > > > + char buf[128];
> > > > > +
> > > > > +
Here are some basic OMAP test results for Linux v3.14-rc3.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.14-rc3/20140217214814/
Test summary
Build: uImage:
Pass ( 3/ 3): omap1_defconfig, omap1_defconfig_1510innovator_only,
omap1_de
On Tue, Feb 18, 2014 at 11:03:35AM -0600, Felipe Balbi wrote:
> On Tue, Feb 18, 2014 at 08:59:11AM -0800, Greg KH wrote:
> > On Tue, Feb 18, 2014 at 10:20:54AM -0600, Felipe Balbi wrote:
> > > On Fri, Jan 17, 2014 at 10:22:35AM +0100, Markus Pargmann wrote:
> > > > debugfs files to show the content
On Tue, Feb 18, 2014 at 08:59:11AM -0800, Greg KH wrote:
> On Tue, Feb 18, 2014 at 10:20:54AM -0600, Felipe Balbi wrote:
> > On Fri, Jan 17, 2014 at 10:22:35AM +0100, Markus Pargmann wrote:
> > > debugfs files to show the contents of important dsps registers.
> > >
> > > Signed-off-by: Markus Parg
On Tue, Feb 18, 2014 at 10:20:54AM -0600, Felipe Balbi wrote:
> On Fri, Jan 17, 2014 at 10:22:35AM +0100, Markus Pargmann wrote:
> > debugfs files to show the contents of important dsps registers.
> >
> > Signed-off-by: Markus Pargmann
> > ---
> > drivers/usb/musb/musb_dsps.c | 54
> > +
On Fri, Jan 17, 2014 at 10:22:35AM +0100, Markus Pargmann wrote:
> debugfs files to show the contents of important dsps registers.
>
> Signed-off-by: Markus Pargmann
> ---
> drivers/usb/musb/musb_dsps.c | 54
>
> 1 file changed, 54 insertions(+)
>
>
> Use a meaningful name for the reference clocks so that it indicates the
> function.
>
> CC: Lee Jones
> CC: Samuel Ortiz
> Signed-off-by: Roger Quadros
> ---
> drivers/mfd/omap-usb-host.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(
On 02/14/2014 03:33 PM, Lee Jones wrote:
Use a meaningful name for the reference clocks so that it indicates the
function.
CC: Lee Jones
CC: Samuel Ortiz
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-host.c | 6 +++---
1 file changed, 3 inse
Hi Igor,
On Tuesday 18 February 2014 16:03:44 Igor Grinberg wrote:
> On 02/18/14 14:47, Laurent Pinchart wrote:
> > On Monday 10 February 2014 22:54:40 Laurent Pinchart wrote:
> >> The camera sensor will soon require regulators and clocks. Register
> >> fixed regulators for its VAA and VDD power s
On Friday 14 February 2014 11:15 AM, Nishanth Menon wrote:
When device is booted using devicetree, platforms impacted by Erratum
2.1.1.128 is not detected easily in the mmc driver. This erratum
indicates that the module cannot do multi-block transfers. Platforms
such as LDP which use OMAP3 ES rev
On Monday 17 February 2014 05:06 PM, Daniel Mack wrote:
This should probably be done implicitly through mmc_of_parse(), but that
doesn't play well along with the multi-slot model the hsmmc driver
features. Hence, for now, do it manually. The properties are already
documented in Documentation/devi
Hi Laurent,
On 02/18/14 14:47, Laurent Pinchart wrote:
> Mauro, Tony,
>
> On Monday 10 February 2014 22:54:40 Laurent Pinchart wrote:
>> The camera sensor will soon require regulators and clocks. Register
>> fixed regulators for its VAA and VDD power supplies and a fixed rate
>> clock for its mas
Mauro, Tony,
On Monday 10 February 2014 22:54:40 Laurent Pinchart wrote:
> The camera sensor will soon require regulators and clocks. Register
> fixed regulators for its VAA and VDD power supplies and a fixed rate
> clock for its master clock.
This patch is a prerequisite for a set of 4 patches t
On Friday 14 February 2014 01:59 PM, Tomi Valkeinen wrote:
Instead of relying on the OMAP specific
omap_pm_get_dev_context_loss_count() to detect register context loss, we
can achieve the same in a much simpler way by just observing the DISPC
registers.
We always set DISPC's load mode to LOAD_FR
HDMI codec dummy entries for Panda/ES.
Signed-off-by: Paolo Pisati
---
Depends on "0f7f3d1 ASoC: hdmi-codec: Add devicetree binding with
documentation", eligible for a 3.14-rcX fix.
arch/arm/boot/dts/omap4-panda-common.dtsi |9 -
arch/arm/boot/dts/omap4-panda-es.dts |3 ++-
On Saturday 15 February 2014 01:51 AM, Mark Brown wrote:
On Thu, Feb 06, 2014 at 11:20:13AM +0530, Keerthy wrote:
This patch adds support for TPS65218 PMIC regulators.
The regulators set consists of 6 DCDCs and 1 LDO. The output
voltages are configurable and are meant to supply power to the
mai
Hello,
> > * I have a test program, http://pmeerw.net/scaler.c, which exercises the
> > OMAP3 ISP resizer standalone with the pipeline given below; it crashes the
> > system quite reliably on 3.7 and recent kernels :(
> >
> > the reason for the crash is that the ISP resizer can still be busy and
25 matches
Mail list logo
