On Wed, Aug 15, 2012 at 01:38:45PM +0100, Srinivas KANDAGATLA wrote:
From: Srinivas Kandagatla srinivas.kandaga...@st.com
This patch allows dtc to strip out nodes in its output based on status
property. Now the dtc has additional long option --strip-disabled to
strip all the nodes which have
On 08/16/2012 10:05 PM, Thomas Abraham wrote:
Add device tree based discovery support for Samsung's sdhci controller
Cc: Ben Dooks ben-li...@fluff.org
Cc: Kukjin Kim kgene@samsung.com
Cc: Chris Ball c...@laptop.org
Signed-off-by: Thomas Abraham thomas.abra...@linaro.org
---
Changes
Hi Thomas,
Am Donnerstag, 16. August 2012, 17:49:29 schrieb Thomas Abraham:
Add device tree based discovery support for Samsung's sdhci controller
Cc: Ben Dooks ben-li...@fluff.org
Cc: Kukjin Kim kgene@samsung.com
Cc: Chris Ball c...@laptop.org
Signed-off-by: Thomas Abraham
On 17/08/12 07:04, David Gibson wrote:
On Wed, Aug 15, 2012 at 01:38:45PM +0100, Srinivas KANDAGATLA wrote:
From: Srinivas Kandagatla srinivas.kandaga...@st.com
This patch allows dtc to strip out nodes in its output based on status
property. Now the dtc has additional long option
This patch series add new property into regulator DT for telling whether or not
to hook pmic's power off routine to system call pm_power_off.
Patch 1 add power off support for Tegra20 boards using TPS6586x
Patch 2 add power off support for Tegra30 boards using TPS65910
Verified on Seaboard
Add DT property ti,system-power-controller telling whether or not this
pmic is in charge of controlling the system power, so the power off
routine can be hooked up to system call pm_power_off.
Based on the work by:
Dan Willemsen dwillem...@nvidia.com
Signed-off-by: Bill Huang bilhu...@nvidia.com
Add DT property ti,system-power-controller telling whether or not this
pmic is in charge of controlling the system power, so the power off
routine can be hooked up to system call pm_power_off.
Based on the work by:
Dan Willemsen dwillem...@nvidia.com
Signed-off-by: Bill Huang bilhu...@nvidia.com
Hello,
On Fri, Aug 17, 2012 at 6:18 AM, Joonyoung Shim dofm...@gmail.com wrote:
Hi Leela.
2012/8/16 Leela Krishna Amudala l.kris...@samsung.com:
The name of the exynos drm fimd device is renamed to exynos-drm-fimd
and two device ids are created for exynos4-fb and exynos5-drm-fimd.
Also,
Hello,
On Fri, Aug 17, 2012 at 6:55 AM, Joonyoung Shim dofm...@gmail.com wrote:
Hi,
2012/8/16 Leela Krishna Amudala l.kris...@samsung.com:
Add device tree based discovery support for DRM-FIMD driver.
Signed-off-by: Leela Krishna Amudala l.kris...@samsung.com
---
On Thu, Aug 16, 2012 at 04:40:59PM +0300, Peter Ujfalusi wrote:
in order to be able to add DT support for the McBSP driver which is used on
all
OMAP platforms (OMAP1/2/3/4/5) I needed to make some cleanups to the stack:
Tony, are you OK with these changes going via ASoC?
Hello,
I think you misinterpreted my question.
Alex,
Your documentation says that power on sequence look like shown below
(step1: enabling regulator, step2: enabling pwm and step3: enabling a
gpio line)
power-on-sequence {
step0 {
regulator = power;
On Thu, Aug 16, 2012 at 04:20:47PM -0600, Grant Likely wrote:
On Aug 16, 2012 3:46 PM, Mitch Bradley w...@firmworks.com wrote:
Is there an established Linux convention for expressing that dual-parent
relationship for I2C? The phandle schemes for cross-tree gpio, clk, and
interrupt
On Fri, Aug 17, 2012 at 02:16:29AM -0700, Bill Huang wrote:
Add DT property ti,system-power-controller telling whether or not this
pmic is in charge of controlling the system power, so the power off
routine can be hooked up to system call pm_power_off.
Based on the work by:
Dan Willemsen
On Thu, Aug 16, 2012 at 11:36:31AM -1000, Mitch Bradley wrote:
The main rule for node names is that a user browsing the device tree
can easily determine what something is. Thus ethernet instead of
DEC,21140.
Does this actually buy us much? It seems like it's something that's
much better
On Monday 13 August 2012, Ian Molton wrote:
On 10/08/12 11:49, Arnd Bergmann wrote:
On Thursday 09 August 2012, Ian Molton wrote:
The driver
already knows all those offsets and they are always the same
for all variants of mv643xx, right?
Yes, but its not clean. And no amount of
On 08/17/2012 12:32 AM, Hiremath, Vaibhav wrote:
On Thu, Aug 16, 2012 at 22:27:42, Hunter, Jon wrote:
On 08/15/2012 04:13 AM, Vaibhav Hiremath wrote:
On 7/14/2012 3:56 AM, Jon Hunter wrote:
OMAP3 devices may or may not have security features enabled. Security
enabled
devices are known
David Gibson wrote:
The name still isn't quite right - it doesn't just strip disabled
nodes but anything that isn't okay, OF defines failed at least as
another possibility for the status property.
I would say that staus=failed in a DTS is an error. It doesn't make any
sense. How can you
* Peter Ujfalusi peter.ujfal...@ti.com [120816 06:41]:
Move the McBSP CLKS re-parenting code to ASoC driver from
arch/arm/mach-omap2.
The call fort the re-parenting has been already limited to OMAP2+ SoC in
the ASoC driver. There is no longer need to have callback function for it.
* Peter Ujfalusi peter.ujfal...@ti.com [120816 06:41]:
On OMAP2430 all McBSP ports have 128 word long buffer, enable the use of
the FIFO for the audio stack.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Acked-by: Jarkko Nikula jarkko.nik...@bitmer.com
---
* Peter Ujfalusi peter.ujfal...@ti.com [120816 06:41]:
am3517evm board uses McBSP1 for audio with 4pin configuration.
The CLKR/FSR signals need to be connected to CLKX/FSX pin of the SoC in
this case.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Acked-by: Jarkko Nikula
* Peter Ujfalusi peter.ujfal...@ti.com [120816 06:41]:
The muxing is done at board level, no need to do it in the ASoC machine
driver.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Acked-by: Jarkko Nikula jarkko.nik...@bitmer.com
Acked-by: Tony Lindgren t...@atomide.com
* Peter Ujfalusi peter.ujfal...@ti.com [120816 06:41]:
Remove the feature to configure the CLKR/FSR mux on McBSP port with 6pin
configuration.
When moving to devicetree these callback can no longer be used in a clean
way anymore.
If a board require to change the 6pin port to work in 4pin
* Peter Ujfalusi peter.ujfal...@ti.com [120816 06:41]:
Only create the devices in a legacy way if we do not have the DT data.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
___
devicetree-discuss mailing
* Mark Brown broo...@opensource.wolfsonmicro.com [120817 03:18]:
On Thu, Aug 16, 2012 at 04:40:59PM +0300, Peter Ujfalusi wrote:
in order to be able to add DT support for the McBSP driver which is used on
all
OMAP platforms (OMAP1/2/3/4/5) I needed to make some cleanups to the stack:
On 8/17/2012 1:36 AM, Mark Brown wrote:
On Thu, Aug 16, 2012 at 11:36:31AM -1000, Mitch Bradley wrote:
The main rule for node names is that a user browsing the device tree
can easily determine what something is. Thus ethernet instead of
DEC,21140.
Does this actually buy us much? It
On some platforms (e.g. MPC5200) a direct 1:1 mapping may cause
problems with JFFS2 usage, as the local bus (LPB) doesn't support
unaligned accesses as implemented in the JFFS2 code via memcpy().
By defining no-unaligned-direct-access, the flash will not be
exposed directly to the MTD users (e.g.
On 08/17/2012 04:14 PM, Jarkko Nikula wrote:
On 08/17/2012 04:07 PM, Tony Lindgren wrote:
* Peter Ujfalusi peter.ujfal...@ti.com [120816 06:41]:
On OMAP2430 all McBSP ports have 128 word long buffer, enable the use of
the FIFO for the audio stack.
Is this the case also for 2420? I thought
On 17/08/12 13:16, Tabi Timur-B04825 wrote:
David Gibson wrote:
The name still isn't quite right - it doesn't just strip disabled
nodes but anything that isn't okay, OF defines failed at least as
another possibility for the status property.
I would say that staus=failed in a DTS is an error.
On 08/17/2012 04:37 AM, Leela Krishna Amudala wrote:
Hello,
I think you misinterpreted my question.
...
But I don't bother about enabling regulator and pwm for my panel.
My panel needs a sequence like
1. Pull up a gpio line
2. Maintain some delay
3. Pull down gpio line
4. Maintain
+devicetree-discuss and lkml
On 08/17/2012 09:51 AM, Mark Langsdorf wrote:
Calxeda highbank SATA phy has intermittent problems bringing up a link
with Gen3 drives. Retrying the phy hard reset can work-around this issue,
but each reset also disables spread spectrum support. The reset function
Srinivas KANDAGATLA wrote:
If you know in advance that device on that SOC is broken, then I guess
Fail/Failed can be used in status property.
One user of this flag in kernel device trees is
./arch/powerpc/boot/dts/mpc8313erdb.dts
/* Remove this (or change to okay) if you have
On 08/17/2012 03:16 AM, Bill Huang wrote:
Add DT property ti,system-power-controller telling whether or not this
pmic is in charge of controlling the system power, so the power off
routine can be hooked up to system call pm_power_off.
Based on the work by:
Dan Willemsen
On 08/17/2012 03:16 AM, Bill Huang wrote:
Add DT property ti,system-power-controller telling whether or not this
pmic is in charge of controlling the system power, so the power off
routine can be hooked up to system call pm_power_off.
Based on the work by:
Dan Willemsen
nvpublic
On Fri, Aug 17, 2012 at 02:16:28AM -0700, Bill Huang wrote:
[...]
diff --git a/drivers/mfd/tps6586x.c b/drivers/mfd/tps6586x.c
[...]
@@ -505,6 +519,11 @@ static int __devinit tps6586x_i2c_probe(struct
i2c_client *client,
goto err_add_devs;
}
+
On Thu, Aug 16, 2012 at 11:10:30AM -1000, Mitch Bradley wrote:
On 8/16/2012 8:38 AM, Stephen Warren wrote:
Device tree bindings shouldn't reference Linux documentation; the
bindings are supposed to be OS-agnostic.
While it is true that bindings should try to be OS-agnostic, there is
the
35 matches
Mail list logo
