On 01/02/13 19:25, Stephen Warren wrote:
> On 02/01/2013 10:27 AM, Stephen Warren wrote:
>> On 02/01/2013 09:51 AM, Rob Herring wrote:
>>> On 02/01/2013 03:01 AM, Srinivas KANDAGATLA wrote:
Hi Stephen,
Not sure if you have already noticed this but,
I did try this patch on my 3.8, and
On Friday 01 February 2013 03:48 PM, Peter De Schrijver wrote:
Signed-off-by: Peter De Schrijver
---
Reviewed-by: Prashant Gaikwad
drivers/clk/tegra/clk.c |1 +
drivers/clk/tegra/clk.h |7 +++
2 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/drivers/clk/tegra/c
On Friday 01 February 2013 03:48 PM, Peter De Schrijver wrote:
Implement most clocks for Tegra114. The super clocks for the CPU complex
are still missing and will be implemented in a future version.
Signed-off-by: Peter De Schrijver
---
drivers/clk/tegra/Makefile |1 +
drivers/clk/
On Sun, Feb 03, 2013 at 18:19:05, Nori, Sekhar wrote:
>
>
> On 1/29/2013 1:08 PM, Vishwanathrao Badarkhe, Manish wrote:
> > Add I2C0 device tree node information to da850-evm.
> > Also, add I2C0 pin muxing information in da850-evm.
> >
> > Signed-off-by: Vishwanathrao Badarkhe, Manish
> > ---
>
On 03/02/2013 22:38, Jon Loeliger wrote:
> Applied, but yeah, I had to clean up an otherwise messy commit message.
>
Sorry, I'd have used git send-email instead but got too lazy and copied
the whole patch.
> And double yeah, I also copied the DTC list where this patch should
> also have been sen
Cho,
On Wed, Jan 02, 2013 at 02:53:49PM +0900, KyongHo Cho wrote:
> On Tuesday, January 1, 2013, Sylwester Nawrocki
> > Cc: devicetree-discuss@lists.ozlabs.org
Since patch 7 of this set is already merged, do you mind to re-post the
rest of this patch-set with the latest comments addressed? I ca
2013. 2. 1. 오후 8:52 Inki Dae 작성:
>
>
>> -Original Message-
>> From: linux-media-ow...@vger.kernel.org [mailto:linux-media-
>> ow...@vger.kernel.org] On Behalf Of Sachin Kamat
>> Sent: Friday, February 01, 2013 8:40 PM
>> To: Inki Dae
>> Cc: Sylwester Nawrocki; Kukjin Kim; Sylwester
Support for loading the simple-card module via devicetree.
It requests cpu/codec information for probing.
Signed-off-by: Kuninori Morimoto
---
v3 -> v4
- dai-name -> port-name and option
- removed sub-node
.../devicetree/bindings/sound/simple-card.txt | 62 +++
sound/soc/gener
Current ASoC always request codec_dai_name for matching,
but it can be option.
This patch set codec_dai_name as option.
Signed-off-by: Kuninori Morimoto
---
sound/soc/soc-core.c | 17 ++---
1 file changed, 6 insertions(+), 11 deletions(-)
diff --git a/sound/soc/soc-core.c b/sound/
On Fri, Feb 1, 2013 at 3:55 AM, Kukjin Kim wrote:
> Rahul Sharma wrote:
>
> [...]
>
>> + hdmi {
>> + compatible = "samsung,exynos4-hdmi14";
>> >>>
>> >>>
>> >>>
>> >>> What "-hdmi14" signifies here ? And to which Exynos4 SoC revisions
> this
>> >>> compatible property
Hi Mark, Stephen
> > > There's more attributes that we might want to configure on the
> > > devices than just the actual DAI link. Clocks for example.
>
> > Sure, but this binding is *simple*-audio, right. If the intent is to
> > create some more general/all-encompassing binding structure, I'd
Hi Stephen, Mark
> > +- simple-audio,dai-name: simple-audio CPU/CODEC DAI
> > name
>
> OK, I see those two are CPU-/CODEC-specific. However, you could easily
> just have different property names for the two.
>
> I assume you didn't like my idea of not putting the DAI names
From: Lars Poeschel
This converts the mcp23s08 driver to be able to be used with device
tree.
There are two properties taken, that correspond to the members of
the struct mcp23s08_platform_data, that is the base member and the
chip array member.
Signed-off-by: Lars Poeschel
---
.../devicetree/
From: Lars Poeschel
I wanted to use mcp23s08 driver with a device that boots using device tree.
Therefore I had to modify the driver to be able to take it's platform_data
from the device tree.
I am using a mcp23017 (I2C) device successfully with the patch booted over
device tree. I am not sure if
On Wed, Jan 30, 2013 at 1:54 AM, Sylwester Nawrocki
wrote:
> Hi,
>
>
> On 01/28/2013 07:44 AM, Rahul Sharma wrote:
+
+ mixer: mixer {
+ compatible = "samsung,exynos4-mixer";
>>>
>>>
>>>
>>> I'm afraid this compatible property it too generic. Is the video mix
Thanks Sylwester,
On Wed, Jan 30, 2013 at 2:12 AM, Sylwester Nawrocki
wrote:
> Hi Rahul,
>
>
> On 01/28/2013 07:19 AM, Rahul Sharma wrote:
--- a/arch/arm/boot/dts/exynos4.dtsi
+++ b/arch/arm/boot/dts/exynos4.dtsi
@@ -289,4 +289,11 @@
interrupts =<
On Thu, Jan 31, 2013 at 10:22 AM, Inki Dae wrote:
> 2013/1/31 Stephen Warren :
>> On 01/30/2013 06:16 PM, Inki Dae wrote:
>>> 2013/1/30 Sylwester Nawrocki :
Hi,
On 01/08/2013 11:56 PM, Stephen Warren wrote:
>
> On 01/08/2013 01:16 PM, Sean Paul wrote:
>>
>> Add
Booting 3.8-rc4 on omap4 panda results in the following error
[0.27] omap_i2c 4807.i2c: did not get pins for i2c error: -19
[0.445770] omap_i2c 4807.i2c: bus 0 rev0.11 at 400 kHz
[0.473937] omap_i2c 48072000.i2c: did not get pins for i2c error: -19
[0.474670] omap_i2c 4
Sorry, sent to the devicetree-discuss list by mistake, anyone who is in
devicetree-discuss list please ignore it.
Best Regards.
Anson huang 黄勇才
Freescale Semiconductor Shanghai
上海浦东新区亮景路192号A座2楼
201203
Tel:021-28937058
$-Original Message-
$From: Huang Yongcai-B20788
$Sent: Friday, Feb
When LDO is set to voltage up, need to do enough waiting before
it ramps up to the new voltage, and this ramp up time should be
based on the register setting.
Signed-off-by: Anson Huang
---
.../bindings/regulator/anatop-regulator.txt|8
drivers/regulator/anatop-regulator.c
some of anatop's regulators(cpu, vddpu and vddsoc) have
register settings about LDO's step time, which will impact
the LDO ramp up speed, need to use set_voltage_time_sel
interface to add necessary delay everytime LDOs' voltage
is increased.
offset 0x170:
bit [24-25]: cpu
bit [26-27]: vddpu
bit [2
some of anatop's regulators(cpu, vddpu and vddsoc) have
register settings about LDO's step time, which will impact
the LDO ramp up speed, need to use set_voltage_time_sel
interface to add necessary delay everytime LDOs' voltage
is increased.
offset 0x170:
bit [24-25]: cpu
bit [26-27]: vddpu
bit [2
Hi, Ezequiel.
I checked with your first patch, that is no ploblem.
you dont need to change patch.
sorry for my noise.
best regards,
Nobuhiro
On Wed, Jan 30, 2013 at 3:56 AM, Ezequiel Garcia wrote:
> Hi Jason,
>
> On Wed, Jan 23, 2013 at 2:40 PM, Jason Cooper wrote:
>> On Wed, Jan 23, 2013 at
Hi Stephen
Thank you for checking patch
> > +Required properties:
> > +
> > +- compatible : "simple-audio"
> > +- simple-audio,card-name : simple-audio card name
> > +- simple-audio,format : see below
> > +
> > +Optional properties:
> > +
> > +- simple-audio,
---
libfdt/fdt.h| 50 ++
libfdt/libfdt_env.h | 50 ++
2 files changed, 100 insertions(+)
mode change 100644 => 100755 libfdt/fdt.h
mode change 100644 => 100755 libfdt/libfdt_env.h
diff --
Add mcspi node and pinmux data for omap5 mcspi controller.
Tested on omap5430 evm with 3.8-rc4 custom kernel.
Signed-off-by: Sourav Poddar
---
Develops this on the patch[1] submitted in mainline
[1]: http://www.spinics.net/lists/kernel/msg1473163.html
arch/arm/boot/dts/omap5-evm.dts | 46
From: Felipe Balbi
Add all 4 mcspi instances to omap5.dtsi file.
Signed-off-by: Felipe Balbi
Signed-off-by: Sourav Poddar
---
arch/arm/boot/dts/omap5.dtsi | 40
1 files changed, 40 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap5.d
Patch series adds omap5 evm mcspi nodes and pinctrl
data in omap5.dtsi and omap5-evm.dts files.
Felipe Balbi (1):
arm: dts: omap5: add SPI devices to OMAP5 DeviceTree file
Sourav Poddar (1):
arm: dts: omap5-evm: Add mcspi data
arch/arm/boot/dts/omap5-evm.dts | 46
some of anatop's regulators(vppcpu, vddpu and vddsoc) have
register settings about LDO's step time, which will impact
the LDO ramp up speed, need to use set_voltage_time_sel
interface to add necessary delay everytime LDOs' voltage
is increased.
offset 0x170:
bit [24-25]: vddcpu
bit [26-27]: vddpu
Support for loading the simple-card module via devicetree.
It requests cpu/codec information for probing.
Signed-off-by: Kuninori Morimoto
---
v2 -> v3
- modify simple-card.txt
- remove "platform" from DT
- DT used sub-node
.../devicetree/bindings/sound/simple-card.txt | 71 +
Hi Luciano,
On Wednesday 30 January 2013 11:55 AM, Luciano Coelho wrote:
Hi Sourav,
On Mon, 2013-01-28 at 16:47 +0530, Sourav Poddar wrote:
Booting 3.8-rc4 om omap 4430sdp results in the following error
omap_i2c 4807.i2c: did not get pins for i2c error: -19
[1.024261] omap_i2c 4807
Hi Stephen, Mark
Thank you for your checking
> >> Rename that simple-audio,dma-controller perhaps? "platform" is a word
> >> specific to ASoC, and the bindings really should be generic across OSs.
(snip)
> I still don't understand why the ASoC platform has to be exposed in
> device tree; it see
Hi Linus,
On Tue, Jan 29, 2013 at 16:29:54, Linus Walleij wrote:
> On Tue, Jan 29, 2013 at 8:38 AM, Vishwanathrao Badarkhe, Manish
> wrote:
>
> > Currently, I2C driver gets probed before pinctrl driver.
> > To achieve I2C pin muxing via pinctrl driver before I2C probe get
> > called, register
Hi Mark, Stephen
>> simple-audio,codec {
>> simple-audio,dev = &phandle;
>> simple-audio,system-clock-frequency = 12288;
>> };
I would like to ask you before creating v3 patch.
I got some opinions from you.
- cpu/codec style (above)
- "controller" naming
Add tps6507x regulator device tree data to da850-evm by
adding regulator consumers with tightened constraints
and regulator-name.TPS6507x regulator handle can be obtained
by using this regulator name.
Regulator constraints are added as per da850 board file.
Regulator names are given as per maximum
Add device tree data for tps6507x regulator by adding
all tps6507x regulator nodes. Regulators are initialized
based on compatible name provided in tps6507x DT file.
All tps6507x PMIC regulator device tree nodes are placed
in a separate device tree include file (tps6507x.dtsi).
tps6507x.dtsi file
Add I2C0 device tree node information to da850-evm.
Also, add I2C0 pin muxing information in da850-evm.
Signed-off-by: Vishwanathrao Badarkhe, Manish
---
Changes since V1:
- Updated i2c0 node names in dts and dtsi file.
- Removed interrupt parent from i2c0 node.
- Handled i2c0 pin mux inside i
Add device tree based initialization support for TI's
tps6507x mfd device.
Signed-off-by: Vishwanathrao Badarkhe, Manish
---
Changes since V1:
- updated subject line for commit.
:100644 100644 409afa2... 5ad4b77... M drivers/mfd/tps6507x.c
drivers/mfd/tps6507x.c |9 +
1 files chan
Add OF_DEV_AUXDATA for I2C0 controller driver in da850 board
dt file to use I2C0 clock.
Signed-off-by: Vishwanathrao Badarkhe, Manish
---
Changes since V1:
- updated name for auxdata lookup
da850_evm_auxdata_lookup -> da850_auxdata_lookup
:100644 100644 37c27af... 95ca4e9... M arch/arm/mach
Currently, I2C driver gets probed before pinctrl driver.
To achieve I2C pin muxing via pinctrl driver before I2C
probe get called, register pinctrl driver in arch_initcall.
Also, add module_exit to unregister pinctrl driver.
Signed-off-by: Vishwanathrao Badarkhe, Manish
---
:100644 100644 f6a360b
This patch series enables device tree support for I2C0
and for regulator via tps6507x mfd device on da850-evm.
Applies on top of v3.8-rc5 of linus tree.
Tested on da850-evm device.
Test procedure followed as below:
Once device boots up, issue command as:
$for reg in /sys/class/regulator/*; do e
On Mon, Jan 28, 2013 at 21:32:13, Nori, Sekhar wrote:
> Hi Mrugesh,
>
> On 1/28/2013 1:17 PM, Mrugesh Katepallewar wrote:
> > Add RTC DT entries in da850 dts file.
> >
> > Signed-off-by: Mrugesh Katepallewar
> > ---
> > Applies on top of v3.8-rc4 of linus tree.
> >
> > This patch is depending o
Hi Mark
> > This patch adds snd_soc_of_parse_daifmt() and supports below style on DT.
>
> Applied, thanks.
Thank you.
Now, I'm afraid about this snd_soc_of_parse_daifmt() patch.
I created this to be possible to share to get SND_SOC_ flags between all
drivers on DT.
But now simple-card is
Hi Mark
> > Sorry, Does this means under Documentation ?
> > Or driver ?
>
> In the binding document.
I see.
> > I guess it can share format between codec/dai,
> > but it is difficult for inversion.
> > Because it is depends on its default clock polarity.
> > of course we can do
> > simple-au
Hi Stephen
Thank you for checking path
> > +Required properties:
> > +
> > +- compatible : "simple-audio"
> > +- simple-audio,card-name : simple-audio card name
> > +
> > +- simple-audio,platform,controller : phandle for platform
>
Hi Mark
Thank you for checking patch
> > +- simple-audio,cpu,dai,clock-gating: if needed, see below
>
> A lot of these are listed as "if needed" - this means they should be
> listed separately as optional properties rather than in the required
> properties section.
Sorry, Does
This patch adds device tree parsing for gpio_ir_recv platform_data and
the mandatory binding documentation. It basically follows what we already
have for e.g. gpio_keys. All required device tree properties are OS
independent but optional properties allow linux specific support for rc
protocols and
Hi
On Sun, Jan 27, 2013 at 09:07:57PM +0100, Hauke Mehrtens (ha...@hauke-m.de)
wrote:
> This fixes the following section mismatch:
>
> WARNING: drivers/w1/masters/w1-gpio.o(.data+0x188): Section mismatch in
> reference from the variable w1_gpio_driver to the function
> .init.text:w1_gpio_probe()
Booting 3.8-rc4 om omap 4430sdp results in the following error
omap_i2c 4807.i2c: did not get pins for i2c error: -19
[1.024261] omap_i2c 4807.i2c: bus 0 rev0.12 at 100 kHz
[1.030181] omap_i2c 48072000.i2c: did not get pins for i2c error: -19
[1.037384] omap_i2c 48072000.i2c: b
Booting 3.8-rc4 om omap 5430evm results in the following error
omap_i2c 4807.i2c: did not get pins for i2c error: -19
[1.024261] omap_i2c 4807.i2c: bus 0 rev0.12 at 100 kHz
[1.030181] omap_i2c 48072000.i2c: did not get pins for i2c error: -19
[1.037384] omap_i2c 48072000.i2c: b
Hi Tomasz,
On Mon, Jan 28, 2013 at 2:14 PM, Tomasz Figa wrote:
> Hi Rahul,
>
> On Monday 28 of January 2013 12:25:27 Rahul Sharma wrote:
>> Hi Thomas,
>>
>> On Fri, Jan 25, 2013 at 11:10 PM, Thomas Abraham
>>
>> wrote:
>> > On 25 January 2013 02:39, Rahul Sharma
> wrote:
>> >> Signed-off-by: Ra
Add RTC DT entries in da850 dts file.
Signed-off-by: Mrugesh Katepallewar
---
Applies on top of v3.8-rc4 of linus tree.
This patch is depending on
"ARM: davinci: da850: add interrupt-parent property in soc node"
https://patchwork.kernel.org/patch/2044101/
Tested on da850-evm device.
Test Proc
Hi Thomas,
On Fri, Jan 25, 2013 at 11:10 PM, Thomas Abraham
wrote:
> On 25 January 2013 02:39, Rahul Sharma wrote:
>> Signed-off-by: Rahul Sharma
>>
>> Conflicts:
>> arch/arm/mach-exynos/mach-exynos4-dt.c
>> ---
>> arch/arm/boot/dts/exynos4.dtsi | 7 +++
>> arch/arm/mach-ex
On Fri, Jan 25, 2013 at 16:52:18, Nori, Sekhar wrote:
> On 1/25/2013 4:34 PM, Katepallewar, Mrugesh wrote:
> > On Fri, Jan 25, 2013 at 16:04:22, Nori, Sekhar wrote:
> >> On 1/25/2013 11:43 AM, Mrugesh Katepallewar wrote:
> >>> Add RTC DT entries in da850 dts file.
> >>>
> >>> Signed-off-by: Mrugesh
Thanks Sachin. Will add related documentation and resend.
On 28 January 2013 11:56, Sachin Kamat wrote:
> Hi Vikas,
>
> You need to CC devicetree-discuss@lists.ozlabs.org for patches adding
> new bindings and add documentation related to it.
>
> On 28 January 2013 11:14, Vikas Sajjan wrote:
>> T
On Mon, Jan 28, 2013 at 2:34 AM, Sylwester Nawrocki
wrote:
> On 01/25/2013 11:39 AM, Rahul Sharma wrote:
>>
>> diff --git a/arch/arm/boot/dts/exynos4.dtsi
>> b/arch/arm/boot/dts/exynos4.dtsi
>> index 6c2c79d..07cb7d4 100644
>> --- a/arch/arm/boot/dts/exynos4.dtsi
>> +++ b/arch/arm/boot/dts/exynos4
On Fri, Jan 25, 2013 at 16:20:13, Nori, Sekhar wrote:
> On 1/24/2013 5:05 PM, Vishwanathrao Badarkhe, Manish wrote:
> > Add I2C0 device tree node information to da850-evm.
> > Also, add I2C0 pin muxing information in da850-evm.
> >
> > Signed-off-by: Vishwanathrao Badarkhe, Manish
> > ---
> > Dep
On Sat, Jan 26, 2013 at 10:42:08, Mark Brown wrote:
> On Fri, Jan 25, 2013 at 06:29:49AM +, Vishwanathrao Badarkhe, Manish
> wrote:
> > On Thu, Jan 24, 2013 at 17:30:51, Mark Brown wrote:
>
> > I too doubt that whether it should be in architecture specific folder,
>
> > My code is in referen
I've been diving into Linux kernel drivers & device trees for a new project &
am looking for some help.
First, is it reasonable/possible to define a PCI (PCIe) device in a device
tree? Seems like you'd have to reference a BAR#s to do this (& still have
addresses mapped by enumeration). A coup
On Fri, Jan 25, 2013 at 16:04:22, Nori, Sekhar wrote:
> On 1/25/2013 11:43 AM, Mrugesh Katepallewar wrote:
> > Add RTC DT entries in da850 dts file.
> >
> > Signed-off-by: Mrugesh Katepallewar
> > ---
> > Applies on top of v3.8-rc4 of linus tree.
> >
> > Tested on da850-evm device.
> >
> > Test
On Thu, 24 Jan 2013, Sean Paul wrote:
> +static int ptn3460_power_up(struct ptn3460_platform_data *pd)
> +{
> + int ret;
> +
> + if (pd->gpio_pd_n > 0)
> + gpio_set_value(pd->gpio_pd_n, 1);
Hi Sean, just a random thing that caught my eye: last I checked 0 is a
valid GPIO numbe
Hi Mark,
On Thu, Jan 24, 2013 at 17:30:51, Mark Brown wrote:
> On Thu, Jan 24, 2013 at 04:25:19PM +0530, Vishwanathrao Badarkhe, Manish
> wrote:
>
> > ---
> > arch/arm/boot/dts/tps6507x.dtsi | 47
> > +++
>
> Why are you putting this in arch/arm?
>
I too
Add RTC DT entries in da850 dts file.
Signed-off-by: Mrugesh Katepallewar
---
Applies on top of v3.8-rc4 of linus tree.
Tested on da850-evm device.
Test Procedure:
date [.]MM.DD-hh:mm[:ss]
hwclock -w
reset board and check system time.
:100644 100644 37dc5a3... b16efd4... M arch/arm/boot/d
Hi Mark, Stephen, and all
> These patches add snd_soc_of_parse_daifmt() and simple-card DT support
>
> Kuninori Morimoto (2):
> ASoC: add snd_soc_of_parse_daifmt() for DeviceTree
> ASoC: simple-card: add Device Tree support
>
> .../devicetree/bindings/sound/simple-card.txt |
Add I2C0 device tree node information to da850-evm.
Also, add I2C0 pin muxing information in da850-evm.
Signed-off-by: Vishwanathrao Badarkhe, Manish
---
Depends on patch
http://comments.gmane.org/gmane.linux.davinci/25993
arch/arm/boot/dts/da850-evm.dts | 15 +++
arch/arm/boot/d
Add OF_DEV_AUXDATA for I2C0 controller driver in da850 board
dt file to use I2C0 clock.
Signed-off-by: Vishwanathrao Badarkhe, Manish
---
arch/arm/mach-davinci/da8xx-dt.c |8 +++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-davinci/da8xx-dt.c b/arch/arm/m
Add device tree data for tps6507x regulator by adding
all tps6507x regulator nodes. Regulators are initialized
based on compatible name provided in tps6507x DT file.
All tps6507x PMIC regulator device tree nodes are placed
in a separate device tree include file (tps6507x.dtsi).
tps6507x.dtsi file
Add device tree based initialization support for
TI's tps6507x regulators.
Add device tree binding document for TI's tps6507x
using datasheet:
http://www.ti.com/lit/ds/symlink/tps65070.pdf
Signed-off-by: Vishwanathrao Badarkhe, Manish
---
Documentation/devicetree/bindings/mfd/tps6507x.txt | 91
Add device tree based initialization support for TI's
tps6507x mfd device.
Signed-off-by: Vishwanathrao Badarkhe, Manish
---
drivers/mfd/tps6507x.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/drivers/mfd/tps6507x.c b/drivers/mfd/tps6507x.c
index 409afa2..5ad4
Add tps6507x regulator device tree data to da850-evm by
adding regulator consumers with tightened constraints
and regulator-name.TPS6507x regulator handle can be obtained
by using this regulator name.
Regulator constraints are added as per da850 board file.
Regulator names are given as per maximum
This patch series enables device tree support for I2C0 and
for regulator via tps6507x mfd device on da850-evm.
Applies on top of v3.8-rc4 of linus tree.
Tested on da850-evm device.
Test procedure followed as below:
Once device boots up, issue command as:
$for reg in /sys/class/regulator/*; do e
This patch adds a device tree vendor prefix for Cirrus Logic, Inc.
Signed-off-by: Alexander Shiyan
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
b/Documentation/devicetree/bindi
>> > Hi!
>> >
>> > There was still no maintainer, that commented, ack'd, nack'd, apply'd the
>> > series. So, this is just a resend.
>> > The patches were tested with:
>> >
>> > - v15 on Tegra by Thierry
>> > - sh-mobile-lcdcfb by Laurent
>> > - MX53QSB by Marek
>> >
Jon,
Will it be possible to do a new DTC release sometime in the near future? I've
integrated libfdt from DTCv1.3.0 into a TI software component that will be
released with a BSD-type license. During the integration I noticed a lot of
applicable fixes have been made on the master since the las
Hi Thomas,
Le Wed, 23 Jan 2013 19:03:52 +0100,
Thomas Petazzoni a écrit :
> On Wed, 23 Jan 2013 14:04:42 -0300, Ezequiel Garcia wrote:
>
> > from the OpenBlocks AX3-4 board dts file, since you mentioned this
> > board uses that USB
> > port for a PCIe connector -- if I understood correctly.
>
>
On Wed 23 January 2013 11:21:24 Sylwester Nawrocki wrote:
> Hi Hans,
>
> On 01/21/2013 11:31 AM, Hans Verkuil wrote:
> [...]
> >> +Required properties
> >> +---
> >> +
> >> +If there is more than one 'port' or more than one 'endpoint' node
> >> following
> >> +properties are requi
On 01/22/2013 04:37 PM, kishon wrote:
> On Tuesday 22 January 2013 07:47 PM, Roger Quadros wrote:
>> On 01/22/2013 11:58 AM, Kishon Vijay Abraham I wrote:
>>> The OMAP glue has been modified to get PHY by phandle for dt boot.
>>>
>>> Signed-off-by: Kishon Vijay Abraham I
>>> ---
>>> drivers/usb/
On 01/22/2013 11:58 AM, Kishon Vijay Abraham I wrote:
> The OMAP glue has been modified to get PHY by phandle for dt boot.
>
> Signed-off-by: Kishon Vijay Abraham I
> ---
> drivers/usb/musb/omap2430.c |7 ++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/usb/
On 01/22/2013 11:58 AM, Kishon Vijay Abraham I wrote:
> New PHY lib APIs like usb_add_phy_dev() and devm_usb_get_phy_dev() are
> used in MUSB (OMAP), in order to make use of the binding information
> provided in the board file (of OMAP platforms).
> All the platforms should be modified similar to t
On 01/22/2013 11:58 AM, Kishon Vijay Abraham I wrote:
> In order to add support for multipe PHY's of the same type, new API's
> for adding PHY and getting PHY has been added. Now the binding
> information for the PHY and controller should be done in platform file
> using usb_bind_phy API. And for g
On Sun, Jan 20, 2013 at 04:24:49PM -0600, Rob Herring wrote:
> On 01/19/2013 07:06 AM, Cong Ding wrote:
> > The memory allocated to ofdma might be a leakage when error occurs.
> >
> > Signed-off-by: Cong Ding
>
> You need to send this to whomever is working on DMA bindings.
Thank you bob, I adde
On 01/21/2013 03:41 PM, kishon wrote:
> Hi,
>
> On Monday 21 January 2013 06:48 PM, Roger Quadros wrote:
>> On 01/16/2013 05:01 PM, Kishon Vijay Abraham I wrote:
>>> The OMAP glue has been modified to get PHY by phandle for dt boot.
>>>
>>> Signed-off-by: Kishon Vijay Abraham I
>>> ---
>>> driv
On 01/21/2013 03:34 PM, kishon wrote:
> On Monday 21 January 2013 06:51 PM, Roger Quadros wrote:
>> On 01/16/2013 05:01 PM, Kishon Vijay Abraham I wrote:
>>> Added an API devm_usb_get_phy_by_phandle(), to get usb phy by passing a
>>> device node phandle value. This function will return a pointer to
On 01/16/2013 05:01 PM, Kishon Vijay Abraham I wrote:
> Added an API devm_usb_get_phy_by_phandle(), to get usb phy by passing a
> device node phandle value. This function will return a pointer to
> the phy on success, -EPROBE_DEFER if there is a device_node for the phandle,
> but the phy has not be
On 01/16/2013 05:01 PM, Kishon Vijay Abraham I wrote:
> The OMAP glue has been modified to get PHY by phandle for dt boot.
>
> Signed-off-by: Kishon Vijay Abraham I
> ---
> drivers/usb/musb/omap2430.c |7 ++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/usb/
Hi Sylwester,
Just two comments...
On Thu January 3 2013 18:09:22 Sylwester Nawrocki wrote:
> From: Guennadi Liakhovetski
>
> Add a V4L2 OF parser, implementing bindings documented in
> Documentation/devicetree/bindings/media/video-interfaces.txt.
>
> Signed-off-by: Guennadi Liakhovetski
> Si
On Thu January 3 2013 18:03:49 Sylwester Nawrocki wrote:
> From: Guennadi Liakhovetski
>
> This patch adds a document describing common OF bindings for video
> capture, output and video processing devices. It is curently mainly
> focused on video capture devices, with data busses defined by
> sta
The memory allocated to ofdma might be a leakage when error occurs.
Signed-off-by: Cong Ding
---
drivers/of/dma.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/of/dma.c b/drivers/of/dma.c
index 59631b2..583e50e3 100644
--- a/drivers/of/dma.c
+++ b/drivers/of/dma.c
@@ -107,6 +107
Hi,
On Sat, Jan 19, 2013 at 9:11 AM, Gregory CLEMENT
wrote:
> On 01/19/2013 01:07 AM, Nobuhiro Iwamatsu wrote:
>> Hi,
>>
>> Thomas, Thank you for the detailed explanation.
>>
>> Ezequiel, I checked your patch on OpenBlocks AX3, work fine.
>>
>> But I have a question. your patch "arm: mvebu: Add s
Hi,
Thomas, Thank you for the detailed explanation.
Ezequiel, I checked your patch on OpenBlocks AX3, work fine.
But I have a question. your patch "arm: mvebu: Add support for USB
host controllers in Armada 370/XP"
was set USB controller of 0xd005 to IRQ 45. I think this is 47,
and 0xd005200
On Fri January 18 2013 16:48:43 Sylwester Nawrocki wrote:
> On 01/03/2013 06:09 PM, Sylwester Nawrocki wrote:
> > From: Guennadi Liakhovetski
> >
> > Add a V4L2 OF parser, implementing bindings documented in
> > Documentation/devicetree/bindings/media/video-interfaces.txt.
> >
> > Signed-off-by:
On Fri, 2013-01-18 at 12:11 +0530, Philip Avinash wrote:
> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
> index eaef5e7..f4209d8 100644
> --- a/arch/arm/boot/dts/am33xx.dtsi
> +++ b/arch/arm/boot/dts/am33xx.dtsi
> @@ -393,5 +393,17 @@
> ti,hwmods
On Fri, Jan 18, 2013 at 6:14 AM, Mugunthan V N wrote:
> On 1/18/2013 3:48 AM, Peter Korsgaard wrote:
>
>> When booting with CONFIG_ARM_APPENDED_DTB (either because of using an old
>> U-Boot, not wanting the hassle of 2 files or when using Falcon fast boot
>> mode in U-Boot), nothing updates the e
On Thursday 17 January 2013 4:02:06 am Greg Ungerer wrote:
> Hi Linus,
>
> (My g...@snapgear.com email no longer gets to me, g...@uclinux.org is
> the best direct email for me now).
>
> On 01/17/2013 09:15 PM, Linus Walleij wrote:
> > On Thu, Jan 10, 2013 at 11:08 AM, Arnd Bergmann wrote:
> >> I'v
On 01/16/2013 05:00 PM, Kishon Vijay Abraham I wrote:
> In order to add support for multipe PHY's of the same type, the API's
> for adding PHY and getting PHY has been changed. Now the binding
> information of the PHY and controller should be done in platform file
> using usb_bind_phy API. And for
Hi Linus,
(My g...@snapgear.com email no longer gets to me, g...@uclinux.org is
the best direct email for me now).
On 01/17/2013 09:15 PM, Linus Walleij wrote:
> On Thu, Jan 10, 2013 at 11:08 AM, Arnd Bergmann wrote:
>
>> I've tried to find platforms that don't yet use GPIOLIB and fortunately
>
On 01/16/2013 05:00 PM, Kishon Vijay Abraham I wrote:
> This is in preparation for the changes in PHY library to support adding
> and getting multiple PHYs of the same type. In the new design, the
> binding information between the PHY and the USB controller should be
> specified in the platform spe
On 01/16/2013 05:00 PM, Kishon Vijay Abraham I wrote:
> New platforms are added which has multiple PHY's (of same type) and
> which has multiple USB controllers. The binding information has to be
> present in the PHY library (otg.c) in order for it to return the
> appropriate PHY whenever the USB c
On Tuesday 08 January 2013 01:02 PM, Laxman Dewangan wrote:
> From: Pritesh Raithatha
>
> This adds a driver for the Tegra114 pinmux, and required
> parameterization data for Tegra114.
>
> The driver uses the common Tegra pincontrol driver utility
> functions to implement the majority of the dri
On 16/01/13 17:36, Mark Rutland wrote:
Hi,
This looks nice and simple, I just have a couple of comment.
Thank you
On Wed, Jan 16, 2013 at 09:48:23AM +, Martin Fuzzey wrote:
Signed-off-by: Martin Fuzzey
---
drivers/w1/masters/mxc_w1.c |9 -
1 files changed, 8 insertions(+),
1 - 100 of 163 matches
Mail list logo
