Hi Alexandre,
On Mon, Jul 09, 2012 at 03:31:43PM -0300, Alexandre Pereira da Silva wrote:
> @@ -38,7 +40,7 @@ struct gpio_keys_button_data {
> struct gpio_keys_polled_dev {
> struct input_polled_dev *poll_dev;
> struct device *dev;
> - struct gpio_keys_platform_data *pdata;
> +
Hi Kukjin Kim & Sunyoung,
thanks for the review comments...
On Wed, Jul 18, 2012 at 2:14 PM, Sunyoung Kang wrote:
> Kukjin Kim wrote:
>>
>>Shaik Ameer Basha wrote:
>>>
>>> Add required clock support for Gscaler for exynos5
>>>
>>Hi,
>>
>>Cc'ed Sunyoung Kang who knows gscaler well in my team.
>>
Hi Sylwester,
On Tue, Jul 17, 2012 at 2:03 AM, Sylwester Nawrocki
wrote:
> Hi Shaik,
>
>
> On 07/16/2012 07:33 AM, Shaik Ameer Basha wrote:
>>
>> +++ b/Documentation/devicetree/bindings/media/exynos5-gsc.txt
>> @@ -0,0 +1,16 @@
>> +* Samsung Exynos5 Gscaler device
>> +
>> +Gscaler is used for s
Hi,
On Thu, Jul 19, 2012 at 11:11 AM, Ajay Kumar Gupta wrote:
> Currently we have one single nop transceiver support as same is
> defined as a global variable in drivers/usb/otg/nop-usb-xceiv.c.
> This need to be changed to support multiple otg controller each
> using nop transceiver on a platfor
Hi,
On Thu, Jul 19, 2012 at 11:11 AM, Ajay Kumar Gupta wrote:
> Added device tree support for nop transceiver driver and updated the
> Documentation with device tree binding information for am33xx platform.
>
> Signed-off-by: Ajay Kumar Gupta
> ---
> .../devicetree/bindings/usb/am33xx-usb.txt
On Thursday 19 July 2012, Tony Prisk wrote:
> Given that there have been no replies to this thread, and the restart patch
> has
> now been accepted using 'wmt' as the vendor namespace - would it be safe to
> assume we should formalize this in the vendor-bindings.txt?
>
> I'd like to try and have
Hi,
On Fri, Jul 13, 2012 at 8:27 PM, Sourav Poddar wrote:
> Add keypad data node in omap4 device tree file.
> Also fill the device tree binding parameters
> with the required value in "omap4-sdp" dts file.
>
> Tested on omap4430 sdp with 3.5-rc6 kernel.
>
> Cc: Tony Lindgren
> Cc: Benoit Cousson
From: Arnd Bergmann [a...@arndb.de]
Sent: 19 July 2012 23:16
To: vt8500-wm8505-linux-ker...@googlegroups.com
Cc: Tony Prisk; Alexey Charkov; devicetree-discuss@lists.ozlabs.org; Russell
King; linux-ker...@vger.kernel.org; linux-arm-ker...@lists.infradead.org
Subject: Re: [PATCH 1/1] Add Wondermedi
From: Alexey Charkov [alch...@gmail.com]
Sent: 20 July 2012 00:12
To: Tony Prisk
Cc: Arnd Bergmann; vt8500-wm8505-linux-ker...@googlegroups.com;
devicetree-discuss@lists.ozlabs.org; Russell King;
linux-ker...@vger.kernel.org; linux-arm-ker...@lists.infradead.org
Subject: Re: [PATCH 1/1] Add Wonde
On Thursday 19 July 2012, Tony Prisk wrote:
> I have no issue with that.
>
> I am mainly concerned with the Wondermedia products at the moment.
>
> Adding device tree support for WM8505 (and WM8650) is my main goal as the
> WM8650
> currently isn't supported and trying to get another board file
___
From: Arnd Bergmann [a...@arndb.de]
Sent: 20 July 2012 00:28
To: Tony Prisk
Cc: vt8500-wm8505-linux-ker...@googlegroups.com; Alexey Charkov;
devicetree-discuss@lists.ozlabs.org; Russell King;
linux-ker...@vger.kernel.org; linux-arm-ker...@lists.infradead.or
Hello Marek,
On Wed, Jul 18, 2012 at 12:21 PM, Marek Szyprowski
wrote:
> Hello,
>
> On Wednesday, July 18, 2012 7:57 AM Leela Krishna Amudala wrote:
>
>> This patch updates the register address offsets and adds SFR definitions
>> for writeback for Samsung's V8 display controller.
>>
>> Signed-off
On Thursday 19 July 2012, Tony Prisk wrote:
> Which brings us back to the original question (and raises another one) - can
> we assume yet that
> 'wmt' will be the vendor-binding for Wondermedia? Also, what are we going to
> use for VIA-based
> SoC's given that VIA is the ticker for VIACOM.
>
>
Hi Tomasz,
On Wed, Jul 18, 2012 at 4:35 PM, Tomasz Figa wrote:
> Hi,
>
> On Wednesday 18 of July 2012 11:27:27 Leela Krishna Amudala wrote:
>> This patch updates the register address offsets and adds SFR definitions
>> for writeback for Samsung's V8 display controller.
>>
>> Signed-off-by: Leela
Hello Marek,
On Wed, Jul 18, 2012 at 12:15 PM, Marek Szyprowski
wrote:
> Hello,
>
> On Wednesday, July 18, 2012 7:57 AM Leela Krishna Amudala wrote:
>
>> This patch adds machine specific support for LCD controller like setting
>> power to LCD
>> and adding LCD platform device.
>>
>> Signed-off-b
Add support for the UHCI companion controller in arch-vt8500.
This patch is based almost entirely off uhci-grlib.c with
additions for device tree support.
Signed-off-by: Tony Prisk
---
drivers/usb/host/Kconfig |4 +-
drivers/usb/host/uhci-hcd.c|5 +
drivers/usb/host/uhci-vt8500
Signed-off-by: Tony Prisk
---
drivers/usb/host/ehci-vt8500.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/host/ehci-vt8500.c b/drivers/usb/host/ehci-vt8500.c
index c1eda73..4ba8f0c 100644
--- a/drivers/usb/host/ehci-vt8500.c
+++ b/drivers/usb/host/e
On Thursday 12 July 2012 11:25:02 Simon Glass wrote:
> This makes it easier to include this header from other headers.
Acked-by: Mike Frysinger
> --- a/include/fdtdec.h
> +++ b/include/fdtdec.h
>
> const u8 *fdtdec_locate_byte_array(const void *blob, int node,
>const
On Thursday 19 July 2012, Tony Prisk wrote:
>
> Signed-off-by: Tony Prisk
> ---
> drivers/usb/host/ehci-vt8500.c |9 +
> 1 files changed, 9 insertions(+), 0 deletions(-)
The addition is straightforward and looks correct, but I would suggest you
also add the new "compatible" values t
On Thursday 19 July 2012, Tony Prisk wrote:
> Add support for the UHCI companion controller in arch-vt8500.
> This patch is based almost entirely off uhci-grlib.c with
> additions for device tree support.
>
> Signed-off-by: Tony Prisk
It looks like this file is basically completely generic, so c
Hi,
On Thu, Jul 19, 2012 at 6:51 PM, Gupta, Ajay Kumar wrote:
> Hi,
>> Signed-off-by: Kishon Vijay Abraham I
>> ---
>> Documentation/devicetree/bindings/usb/omap-usb.txt | 34 -
>> drivers/usb/musb/omap2430.c| 55
>>
>> 2 files change
From: Alexey Charkov [alch...@gmail.com]
Sent: 20 July 2012 02:45
To: vt8500-wm8505-linux-ker...@googlegroups.com
Cc: Arnd Bergmann; linux-arm-ker...@lists.infradead.org;
devicetree-discuss@lists.ozlabs.org; Tony Prisk
Subject: Re: [PATCH 1/2] ARM: vt8500: Update vt8500-ehci driver to support
dev
From: Alexey Charkov [alch...@gmail.com]
Sent: 20 July 2012 02:45
To: vt8500-wm8505-linux-ker...@googlegroups.com
Cc: Arnd Bergmann; linux-arm-ker...@lists.infradead.org;
devicetree-discuss@lists.ozlabs.org; Tony Prisk
Subject: Re: [PATCH 1/2] ARM: vt8500: Update vt8500-ehci driver to support
dev
This is a continuous effort of Richard's work [1]. But that generic
cpufreq driver has been rewritten with taking omap-cpufreq.c as the
reference to adopt OPP library.
Same as Richard's patch, the driver has no intention to support the
multi-core systems that frequency and voltage can be scaled
i
From: Richard Zhao
If CONFIG_SMP, cpufreq skips loops_per_jiffy update, because different
arch has different per-cpu loops_per_jiffy definition.
Signed-off-by: Richard Zhao
Acked-by: Russell King
---
arch/arm/kernel/smp.c | 54 +
1 files chang
With a lot of devices booting from device tree nowadays, it requires
that OPP table can be initialized from device tree. The patch adds
a helper function of_init_opp_table together with a binding doc for
that purpose.
Signed-off-by: Shawn Guo
---
Documentation/devicetree/bindings/power/opp.txt
It adds a generic cpufreq driver for CPU0 frequency management based on
clk, regulator, OPP and device tree support. It can support both
uniprocessor (UP) and those symmetric multiprocessor (SMP) systems which
share clock and voltage across all CPUs.
Signed-off-by: Shawn Guo
---
.../devicetree/
Hi Rafael,
On Wed, Jul 18, 2012 at 09:36:43PM +0200, Rafael J. Wysocki wrote:
> On Wednesday, July 18, 2012, Shawn Guo wrote:
> > With a lot of devices booting from device tree nowadays, it requires
> > that OPP table can be initialized from device tree. The patch adds
> > a helper function of_in
Add support for the UHCI companion controller in arch-vt8500.
This patch is based almost entirely off uhci-grlib.c with
additions for device tree support.
Signed-off-by: Tony Prisk
---
drivers/usb/host/Kconfig| 11 +++-
drivers/usb/host/uhci-hcd.c |5 ++
drivers/usb/host/uhci-of.c |
Signed-off-by: Tony Prisk
---
.../devicetree/bindings/usb/vt8500-ehci.txt| 12
drivers/usb/host/ehci-vt8500.c |9 +
2 files changed, 21 insertions(+), 0 deletions(-)
create mode 100644 Documentation/devicetree/bindings/usb/vt8500-ehci.txt
d
Hi,
On Thursday, July 19, 2012, Shawn Guo wrote:
> This is a continuous effort of Richard's work [1]. But that generic
> cpufreq driver has been rewritten with taking omap-cpufreq.c as the
> reference to adopt OPP library.
>
> Same as Richard's patch, the driver has no intention to support the
>
On 19 July 2012 09:21, Seungwon Jeon wrote:
> Hi,
>
> This version does not seems to consider previous reviews fully.
> Could you check the comments below?
I did try to address all the comments. I will check again and resubmit
if I have missed anything.
>
> July 12, 2012, Thomas Abraham wrote:
On 19 July 2012 20:58, Jaehoon Chung wrote:
> Hi Thomas,
>
> I think not good that added the samsung specific code into dw_mmc-pltfm.c
> How about separating to dw-mmc-exynos.c?
I am not sure of this. The only samsung specific code in
dw_mmc-pltfm.c file is the data for of_device_id instances. Th
Replace code in board-dnskw with the equivalent devicetree bindings.
Signed-off-by: Jamie Lentin
---
arch/arm/boot/dts/kirkwood-dns320.dts | 25 +
arch/arm/boot/dts/kirkwood-dns325.dts | 25 +
arch/arm/mach-kirkwood/board-dnskw.c | 90 -
3 f
Thanks to sterling work by Andrew Lunn, more code has been turned into
devicetree bindings. The following takes what he's done, moves common
parts into a DT include file, adds LED and key bindings for both the
DNS320 and DNS325. It has been tested on both devices.
This patchset replaces the DNS32
From: Andrew Lunn
Now that we have I2C support in DT, describe the LM75 in
the DT file for the DNS325.
Signed-off-by: Andrew Lunn
Signed-off-by: Jamie Lentin
---
arch/arm/boot/dts/kirkwood-dns325.dts |8
arch/arm/mach-kirkwood/board-dnskw.c | 15 ++-
2 files change
A lot of device setup is shared between DNS-320 and DNS-325, move the
definitions into a common include.
Signed-off-by: Jamie Lentin
---
arch/arm/boot/dts/kirkwood-dns320.dts | 42 +
arch/arm/boot/dts/kirkwood-dns325.dts | 42 +
arch/ar
Move description of GPIO keys on both the DNS320 and DNS325 into DT.
Signed-off-by: Jamie Lentin
---
arch/arm/boot/dts/kirkwood-dnskw.dtsi | 21 +++
arch/arm/mach-kirkwood/board-dnskw.c | 37 -
2 files changed, 21 insertions(+), 37 deletions(-
Thomas Abraham wrote:
>
> On 19 July 2012 20:58, Jaehoon Chung wrote:
> > Hi Thomas,
> >
> > I think not good that added the samsung specific code into dw_mmc-
> pltfm.c
> > How about separating to dw-mmc-exynos.c?
>
> I am not sure of this. The only samsung specific code in
> dw_mmc-pltfm.c fil
On Thu, Jul 19, 2012 at 08:39:39PM +0200, Rafael J. Wysocki wrote:
> It is too late to consider your patches for inclusion into v3.6, so I'm
> regarding them as RFC at this point.
>
Yes, it's on the review stage, and 3.7 is the target.
> Please resubmit after v3.6-rc1 has been released.
>
Will d
On Thursday, July 19, 2012 10:35 PM, Tomasz Figa wrote:
>
> Hi Leela,
>
> On Thursday 19 of July 2012 18:30:44 Leela Krishna Amudala wrote:
> > Hi Tomasz,
> >
> > On Wed, Jul 18, 2012 at 4:35 PM, Tomasz Figa
> wrote:
> > > Hi,
> > >
> > > On Wednesday 18 of July 2012 11:27:27 Leela Krishna Amuda
On Fri, Jul 20, 2012 at 7:51 AM, Jingoo Han wrote:
> On Thursday, July 19, 2012 10:35 PM, Tomasz Figa wrote:
>>
>> Hi Leela,
>>
>> On Thursday 19 of July 2012 18:30:44 Leela Krishna Amudala wrote:
>> > Hi Tomasz,
>> >
>> > On Wed, Jul 18, 2012 at 4:35 PM, Tomasz Figa
>> wrote:
>> > > Hi,
>> > >
>
On Tue, 2012-07-17 at 19:24 +, Arnd Bergmann wrote:
> On Friday 13 July 2012, Vinod Koul wrote:
> > > Do you mean there must be a global table, or are you ok with putting
> > > the information about a channel into the device that uses the channel,
> > > as we do for most other subsystems (IRQ,
Added device tree support for omap musb driver and updated the
Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I
---
Documentation/devicetree/bindings/usb/omap-usb.txt | 34 +++-
drivers/usb/musb/omap2430.c| 54 +
The mailbox register for usb otg in omap is present in control module.
On detection of any events VBUS or ID, this register should be written
to send the notification to musb core.
Till we have a separate control module driver to write to control module,
omap2430 will handle the register writes to
Add twl4030-usb data node in twl4030 device tree file.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/twl4030.dtsi | 21 +
1 file changed, 21 insertions(+)
diff --git a/arch/arm/boot/dts/twl4030.dtsi b/arch/arm/boot/dts/twl4030.dtsi
index 22f4d13..761a5a5 1006
Add usb otg data node in omap4/omap3 device tree file. Also update
the node with board specific setting in omapx-.dts file.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap3-beagle.dts |6 ++
arch/arm/boot/dts/omap3-evm.dts|6 ++
arch/arm/boot/dts/omap3.dtsi
Add device tree support for twl4030 usb driver.
Update the Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I
---
.../devicetree/bindings/usb/twl-usb.txt| 19 ++
drivers/usb/otg/twl4030-usb.c | 26 +++
All the unnessary functions in omap-phy-internal is removed.
These functionality are now handled by omap-usb2 phy driver.
Cc: Felipe Balbi
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Tony Lindgren
---
arch/arm/mach-omap2/omap_phy_internal.c | 138 ---
arch/arm/
All phy related programming like enabling/disabling the clocks, powering
on/off the phy is taken care of by this driver. It is also used for OTG
related functionality like srp.
This also includes device tree support for usb2 phy driver and
the documentation with device tree binding information is
Add omap-usb2 data node in omap4 device tree file.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap4.dtsi |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 29c6243..15f1890 100644
--- a/arch/arm/boot/dts/
Add twl6030-usb data node in twl6030 device tree file
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap4-panda.dts |4
arch/arm/boot/dts/omap4-sdp.dts |4
arch/arm/boot/dts/twl6030.dtsi|6 ++
3 files changed, 14 insertions(+)
diff --git a/arch/arm/
This patch series adds device tree support for MUSB and device
tree support for all the related modules to get MUSB working in
OMAP platform.
A new omap-usb2 phy driver has been added (with only dt suppport)
to perform phy configurations. Previously this configuration was
performed by twl6030, usi
Add device tree support for twl6030 usb driver.
Update the Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I
---
.../devicetree/bindings/usb/twl-usb.txt| 22 +++
drivers/usb/otg/twl6030-usb.c | 39 +-
All the PHY configuration other than VBUS, ID GND and OTG SRP are removed
from twl6030. The phy configurations are taken care by the dedicated
usb2 phy driver. So twl6030 is made as comparator driver for VBUS and
ID detection.
Writing to control module which is now handled in omap2430.c should be
On Thu, Jul 19, 2012 at 10:54 AM, Shawn Guo wrote:
> With a lot of devices booting from device tree nowadays, it requires
> that OPP table can be initialized from device tree. The patch adds
> a helper function of_init_opp_table together with a binding doc for
> that purpose.
nice to see this hap
Hello,
On Thursday, July 19, 2012 3:22 PM Leela Krishna Amudala wrote:
> Hello Marek,
>
> On Wed, Jul 18, 2012 at 12:15 PM, Marek Szyprowski
> wrote:
> > Hello,
> >
> > On Wednesday, July 18, 2012 7:57 AM Leela Krishna Amudala wrote:
> >
> >> This patch adds machine specific support for LCD con
Hello,
On Thursday, July 19, 2012 2:44 PM Leela Krishna Amudala
> Hello Marek,
>
> On Wed, Jul 18, 2012 at 12:21 PM, Marek Szyprowski
> wrote:
> > Hello,
> >
> > On Wednesday, July 18, 2012 7:57 AM Leela Krishna Amudala wrote:
> >
> >> This patch updates the register address offsets and adds SF
What prompted this patch is that in dma_pool_create() we call
dev_to_node() before checking whether "dev" is NULL. It looks like
there are places which call dma_pool_create() with a NULL pointer. An
example is in drivers/usb/gadget/amd5536udc.c.
Signed-off-by: Dan Carpenter
---
Static checker f
59 matches
Mail list logo