On Thu, Oct 18, 2012 at 18:56:39, Porter, Matt wrote:
...snip...
...snip...
...snip...
>
> This series adds DMA Engine support for AM33xx, which uses
> an EDMA DMAC. The EDMA DMAC has been previously supported by only
> a private API implementation (much like the situation with OMAP
> DMA) found
Hi Linus, thanks for the reply!
On Monday 05 November 2012 02:04:33 Linus Walleij wrote:
> On Wed, Oct 31, 2012 at 10:04 AM, Alex Courbot wrote:
> > Would anyone be opposed to having a gpio_get() function that works
> > similarly to e.g. regulator_get() and clk_get()?
>
> I understand the concep
Hi Mike,
Thanks for your review.
On 30 October 2012 22:00, Mike Turquette wrote:
> Hi Thomas,
>
> Quoting Thomas Abraham (2012-10-07 10:10:51)
>> +/* determine the output clock speed of the pll */
>> +static unsigned long samsung_pll_clock_recalc_rate(struct clk_hw *hw,
>> +
On Sun, Nov 04, 2012 at 23:07:44, Linus Walleij wrote:
> On Tue, Oct 30, 2012 at 3:12 PM, AnilKumar, Chimata wrote:
>
> > I completely understood this named modes, I have added named
> > modes like this in am335x-xxx.dts files
>
> I do not understand how the pinctrl-single dts files work actuall
From: Ajay Kumar Gupta
Device tree node for usbss on AM33XX. There are two musb
controllers on am33xx platform so have port0-mode and
port1-mode data.
[af...@ti.com: reg & interrupt property addition]
Signed-off-by: Ajay Kumar Gupta
Signed-off-by: Santhapuri, Damodar
Signed-off-by: Ravi Babu
Hi Mark Brown,
On 11/2/2012 22:24, Mark Brown wrote:
On Fri, Nov 02, 2012 at 10:34:21AM +0800, Bo Shen wrote:
On 11/1/2012 22:43, Mark Brown wrote:
On Wed, Oct 31, 2012 at 03:26:59PM +0800, Bo Shen wrote:
+dai: dai {
+ compatible = "atmel,atmel-ssc-dai";
+ atmel,dai-master = <&s
Hi Jean-Christophe,
Some minor comments below.
On 4 November 2012 19:10, Jean-Christophe PLAGNIOL-VILLARD
wrote:
> Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD
> Cc: Nicolas Ferre
> Cc: Joachim Eastwood
> Cc: net...@vger.kernel.org
> ---
> .../devicetree/bindings/net/cdns-emac.txt
On 11/02/2012 09:43 AM, Pantelis Antoniou wrote:
[...]
And then use the standard DT support to create later the platform_device that
does represent the new super-cape devices.
We know this is the ideal case. In fact that's the long term goal and we had
internal discussions about it.
Sinc
Hi Daniel,
* Daniel Mack, November 03, 2012 1:06 AM:
> I'm testing these patches with an AM33xx board that has the first musb
> port wired to an USB type A plug, but it doesn't yet work for me.
> So there is no host interface registered. I'm unsure on how to fix this,
> and I didn't get an answe
>
> On 02.11.2012 17:31, Afzal Mohammed wrote:
> > This series adds usb support to am335x SoC's found on boards like
> > Beagle Bone. Here only first instance is supported, as currently
> > multiple phy's of same type is not supported (am335x has two USB2
> > phy's).
>
> I'm testing these patc
From: "Santhapuri, Damodar"
am335x uses nop transceiver driver and need to enable builtin phy
by writing into usb_ctrl register available in system control
module register space. This is being added at musb glue driver
layer until a separate system control module driver is available.
Proper solu
OMAP2+ family of devices are now obtaining resources via DT, earlier
it was obtained from hwmod. Update binding document accrodingly, while
at it add example.
Signed-off-by: Afzal Mohammed
---
.../devicetree/bindings/usb/am33xx-usb.txt | 21 +
1 file changed, 21 inse
dsps wrapper is now dt only. This requires that resources be obtained
using index and not name, modify accordingly.
Signed-off-by: Afzal Mohammed
---
drivers/usb/musb/musb_dsps.c | 14 ++
1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/drivers/usb/musb/musb_dsps.c b/dri
Currently multiple phy's of the same type are not supported, hence
reduce musb instances to one. This helps in supporting at least one
instance of musb, rather than having none. Even without this, it was
observed that both instances were working (by luck), but this holds
good iff wrapper is part of
dsps wrapper is dt only, it cannot execute platform callbacks.
Presence of this would cause NULL dereference, hence remove it.
Signed-off-by: Afzal Mohammed
---
drivers/usb/musb/musb_dsps.c | 26 --
1 file changed, 26 deletions(-)
diff --git a/drivers/usb/musb/musb_dsps.
Hi Balbi,
This series adds usb support to am335x SoC's found on boards like
Beagle Bone. Here only first instance is supported, as currently
multiple phy's of same type is not supported (am335x has two USB2
phy's).
This series is based on your musb branch,
(HEAD - 2f77116 usb: musb: remove hand-
On Fri, Nov 02, 2012 at 04:12:21PM +0100, Lars-Peter Clausen wrote:
> On 11/02/2012 02:38 PM, Josh Cartwright wrote:
> > On Fri, Nov 02, 2012 at 10:33:44AM +0100, Lars-Peter Clausen wrote:
> >> On 10/31/2012 07:58 PM, Josh Cartwright wrote:
[...]
> >>> +static void __init zynq_periph_clk_setup(stru
On Fri, Nov 02, 2012 at 10:20:33AM +0100, Lars-Peter Clausen wrote:
> On 10/31/2012 08:28 PM, Josh Cartwright wrote:
> > Add support for specifying clock information for the uart clk via the
> > device tree. This eliminates the need to hardcode rates in the device
> > tree.
> >
> > Signed-off-by:
Thanks for the review.
On Fri, Nov 02, 2012 at 10:33:44AM +0100, Lars-Peter Clausen wrote:
> On 10/31/2012 07:58 PM, Josh Cartwright wrote:
> > [...]
> > +#define PERIPH_CLK_CTRL_SRC(x) (periph_clk_parent_map[((x)&3)>>4])
> > +#define PERIPH_CLK_CTRL_DIV(x) (((x)&0x3F00)>>8)
>
> A few mor
Hi Alan,
On Nov 2, 2012, at 1:21 PM, Alan Cox wrote:
Fair enough. But there's no such thing a 'hotplug enumeration
construct' in Linux yet, and a bus is the closest thing to it. It does
take advantage of the nice way device code matches drivers and devices
though.
>
> A bus i
Hi Benoit,
On Nov 2, 2012, at 10:15 AM, Cousson, Benoit wrote:
> On 11/1/2012 1:00 PM, Koen Kooi wrote:
>> tl;dr: please suggest an actual solution that allows plug&play when plugging
>> in multiple capes and applying power after that. Preferably one that doesn't
>> pass the buck to u-boot.
>>
Adding the phy driver support to hsotg driver. Keeping the platform data
for continuing the smooth operation for boards which still uses it.
Signed-off-by: Praveen Paneri
---
drivers/usb/gadget/s3c-hsotg.c | 37 +++--
1 files changed, 27 insertions(+), 10 deleti
On Thu, Nov 01, 2012 at 01:46:26, Balbi, Felipe wrote:
> Hi,
>
> On Thu, Nov 01, 2012 at 01:21:36AM +0530, Venkatraman S wrote:
> > On Wed, Oct 31, 2012 at 5:56 PM, Felipe Balbi wrote:
> > > Hi,
> > >
> > > On Wed, Oct 31, 2012 at 05:27:36PM +0530, Hebbar, Gururaja wrote:
> > >> HSMMC IP on AM33x
On Wed, Oct 31, 2012 at 8:14 PM, Lukasz Majewski wrote:
> Hi Felipe,
>
>> Hi,
>>
>> On Tue, Oct 30, 2012 at 10:27:34AM +0530, Praveen Paneri wrote:
>> > @@ -3501,20 +3511,27 @@ static int __devinit s3c_hsotg_probe(struct
>> > platform_device *pdev) int ret;
>> > int i;
>> >
>> > - plat = pde
On Wed, Oct 31, 2012 at 01:56:14PM -0600, Josh Cartwright wrote:
> Add support for retrieving TTC configuration from device tree. This
> includes the ability to pull information about the driving clocks from
> the of_clk bindings.
>
> Signed-off-by: Josh Cartwright
> ---
> diff --git a/drivers/c
Hi Mark Brown,
On 11/1/2012 22:43, Mark Brown wrote:
On Wed, Oct 31, 2012 at 03:26:59PM +0800, Bo Shen wrote:
+Required properties:
+ - compatible: "atmel,atmel-ssc-dai"
+ - atmel,dai-master: this dai base on which ssc controller
+Example:
+dai: dai {
+ compatible = "atmel,atmel-ssc
From: Balbi, Felipe
Sent: Thursday, November 01, 2012 3:51 PM
To: Munegowda, Keshava
Cc: Tony Lindgren; linux-o...@vger.kernel.org;
devicetree-discuss@lists.ozlabs.org; linux-...@vger.kernel.org;
linux-...@vger.kernel.org; Balbi, Felipe; sa...@linux.intel
Linus Walleij writes:
> On Wed, Oct 31, 2012 at 9:10 PM, Kevin Hilman
> wrote:
>
>> Linus Walleij writes:
>
>
>>
>> > piece of hardware, this would be the right thing to do,
>> > and I think the in-kernel examples are all "simple",
>> > e.g. arch/arm/mach-omap2/powerdomain* is all about
>> > po
On 01/11/12 01:38, Rob Herring wrote:
> On 10/31/2012 11:13 AM, James Hogan wrote:
>> @@ -34,7 +35,7 @@ nintendo Nintendo
>> nvidia NVIDIA
>> nxp NXP Semiconductors
>> picochipPicochip Ltd
>> -powervr Imagination Technologies
>> +powervr PowerVR (Imagination Technologies Ltd.)
From: Tony Lindgren [t...@atomide.com]
Sent: Wednesday, October 31, 2012 11:59 PM
To: Munegowda, Keshava
Cc: linux-o...@vger.kernel.org; devicetree-discuss@lists.ozlabs.org;
linux-...@vger.kernel.org; linux-...@vger.kernel.org; Balbi, Felipe;
sa...@linux.
On 11/1/2012 3:30 AM, Arnd Bergmann wrote:
Thanks for the quick replies. I hope I managed to explain the I/O space accesses
now.
Yes, I understood now :)
Also looked into pci_ioremap_io. Things are clear now.
Will send V2 after incorporating all comments.
Regards
Pratyush
_
From: Wei Yongjun
The dereference should be moved below the NULL test.
dpatch engine is used to auto generate this patch.
(https://github.com/weiyj/dpatch)
Signed-off-by: Wei Yongjun
---
drivers/usb/host/ehci-tegra.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/
From: Wei Yongjun
Remove duplicated include.
dpatch engine is used to auto generate this patch.
(https://github.com/weiyj/dpatch)
Signed-off-by: Wei Yongjun
---
drivers/mmc/host/sdhci-dove.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/mmc/host/sdhci-dove.c b/drivers/mmc/host/sd
From: Wei Yongjun
In case of error, the function clk_get() returns ERR_PTR()
and never returns NULL. The NULL test in the return value
check should be replaced with IS_ERR().
dpatch engine is used to auto generate this patch.
(https://github.com/weiyj/dpatch)
Signed-off-by: Wei Yongjun
---
dr
On Wed, Oct 31, 2012 at 3:07 PM, Pantelis Antoniou
wrote:
>
> On Oct 31, 2012, at 11:55 PM, Russ Dill wrote:
>
>> On Wed, Oct 31, 2012 at 9:52 AM, Pantelis Antoniou
>> wrote:
>>> Introducing capebus; a bus that allows small boards (capes) to connect
>>> to a complex SoC using simple expansion con
Add support for COMMON_CLK, and provide simplified models for the
necessary clocks on the zynq-7000. Currently, the PLLs, the CPU clock
network, and the basic peripheral clock networks (for SDIO, SMC, SPI,
QSPI, UART) are modelled.
Signed-off-by: Josh Cartwright
---
.../devicetree/bindings/cloc
Add support for retrieving TTC configuration from device tree. This
includes the ability to pull information about the driving clocks from
the of_clk bindings.
Signed-off-by: Josh Cartwright
---
arch/arm/boot/dts/zynq-7000.dtsi | 53
arch/arm/boot/dts/zynq-zc702.dts | 10 ++
drivers/
This patchset implements COMMON_CLK support for the zynq. At this
point, only the basic fundamental clocks are modelled, and only
passively; for rate calculation. of_clk bindings are implemented to
allow specifying clock/peripheral relationships in the device tree.
Patch 1 and 2 are a followup t
Suggested cleanup by Arnd Bergmann. Move the ttc timer.c code to
drivers/clocksource, and out of the mach-zynq directory.
The common.h (which only held the timer declaration) was renamed to
xilinx_ttc.h and moved into include/linux.
Signed-off-by: Josh Cartwright
Cc: Arnd Bergmann
---
arch/ar
Add support for specifying clock information for the uart clk via the
device tree. This eliminates the need to hardcode rates in the device
tree.
Signed-off-by: Josh Cartwright
---
arch/arm/boot/dts/zynq-7000.dtsi | 4 ++--
drivers/tty/serial/xilinx_uartps.c | 30 +---
The Zynq platform requires the use of CONFIG_OF. Remove the #ifdef
conditionals in the uartps driver.
Signed-off-by: Josh Cartwright
---
drivers/tty/serial/xilinx_uartps.c | 9 -
1 file changed, 9 deletions(-)
diff --git a/drivers/tty/serial/xilinx_uartps.c
b/drivers/tty/serial/xilinx
Move the sys_timer definition out of ttc driver and make it part of the
common zynq code. This is preparation for renaming and COMMON_CLK
support.
Signed-off-by: Josh Cartwright
---
arch/arm/mach-zynq/common.c | 13 +
arch/arm/mach-zynq/common.h | 4 +---
arch/arm/mach-zynq/timer.c
The zynq-7000 has an additional UART at 0xE0001000. Describe it in the
device tree.
Signed-off-by: Josh Cartwright
---
arch/arm/boot/dts/zynq-ep107.dts | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/zynq-ep107.dts b/arch/arm/boot/dts/zynq-ep107.dts
index 574bc04..5
The purpose of the created zynq-7000.dtsi file is to describe the
hardware common to all Zynq 7000-based boards. Also, get rid of the
zynq-ep107 device tree, since it is not hardware anyone can purchase.
Add a zc702 dts file based on the zynq-7000.dtsi. Add it to the
dts/Makefile so it is built
On Oct 31, 2012, at 11:55 PM, Russ Dill wrote:
> On Wed, Oct 31, 2012 at 9:52 AM, Pantelis Antoniou
> wrote:
>> Introducing capebus; a bus that allows small boards (capes) to connect
>> to a complex SoC using simple expansion connectors.
>>
[snip]
>> + if (drv) {
>> + /* ca
Hi Russ,
On Oct 31, 2012, at 11:56 PM, Russ Dill wrote:
> On Wed, Oct 31, 2012 at 9:52 AM, Pantelis Antoniou
> wrote:
>> Capebus is created to address the problem of many SoCs that can provide a
>> multitude of hardware interfaces but in order to keep costs down the main
>> boards only support a
On Wed, Oct 31, 2012 at 9:52 AM, Pantelis Antoniou
wrote:
> Capebus is created to address the problem of many SoCs that can provide a
> multitude of hardware interfaces but in order to keep costs down the main
> boards only support a limited number of them. The rest are typically brought
> out to
On Wed, Oct 31, 2012 at 9:52 AM, Pantelis Antoniou
wrote:
> Introducing capebus; a bus that allows small boards (capes) to connect
> to a complex SoC using simple expansion connectors.
>
> Up to now to support these kind of boards, one had to hack the board files,
> and do all sort of gymnastics t
Linus Walleij writes:
> On Tue, Oct 30, 2012 at 12:34 PM, Mark Brown
> wrote:
>> On Sun, Oct 28, 2012 at 09:12:52PM +0100, Linus Walleij wrote:
>
>>> Moving this handling to bus code or anywhere else
>>> invariably implies that resource acquisition/release order
>>> does not matter, and my point
On Oct 31, 2012, at 7:55 PM, Tony Lindgren wrote:
> * Pantelis Antoniou [121031 10:41]:
>> Introduce beaglebone capebus board support.
> ...
>
>> --- /dev/null
>> +++ b/drivers/capebus/boards/Kconfig
>> @@ -0,0 +1,6 @@
>> +config CAPEBUS_BONE_CONTROLLER
>> +bool "Beaglebone capebus board co
Small summary of capebus.
Signed-off-by: Pantelis Antoniou
---
Documentation/capebus/capebus-summary | 40 +++
1 file changed, 40 insertions(+)
create mode 100644 Documentation/capebus/capebus-summary
diff --git a/Documentation/capebus/capebus-summary
b/Documen
Describe capebus DT bindings in detail.
Signed-off-by: Pantelis Antoniou
---
.../capebus/bone-capebus-slot-override.txt | 28 +++
.../devicetree/bindings/capebus/bone-capebus.txt | 50 +++
.../bindings/capebus/bone-geiger-cape.txt | 78 +
.../bindin
Update the common beaglebone's DTS with the required DT
entries for all known working capes as of now.
Signed-off-by: Pantelis Antoniou
---
arch/arm/boot/dts/am335x-bone-common.dtsi | 689 --
1 file changed, 659 insertions(+), 30 deletions(-)
diff --git a/arch/arm/bo
The "powervr" prefix which is currently described as "Imagination
Technologies" isn't really appropriate for non-PowerVR hardware, so
change the description of "powervr" to "PowerVR (Imagination
Technologies Ltd.)", and add a separate "img" prefix for "Imagination
Technologies Ltd.".
Signed-off-by
Hi Steffen,
On Wed, Oct 31, 2012 at 14:58:05, Steffen Trumtrar wrote:
> Add a function to convert from the generic videomode to a fb_videomode.
>
> Signed-off-by: Steffen Trumtrar
> ---
> drivers/video/fbmon.c | 36
> include/linux/fb.h|2 ++
> 2 f
Support beaglebone's geiger cape.
The geiger cape allows you to measure the amount of
ionising radiation in your area, and as an example
of how to create a complex non-generic cape driver.
Signed-off-by: Pantelis Antoniou
---
drivers/capebus/capes/Kconfig| 7 +
drivers/capebus/cap
Introducing beaglebone generic cape support.
With this you can create almost any kind of cape driver
that doesn't require complex interconnection of the parts.
Most beaglebone capes can be created with this, including
all the display capes (DVI/VGA/LCD) with touchscreen or not,
capes that only us
Introduce beaglebone capebus board support.
This patch creates the beaglebone's board cape bus controller.
The board controller is responsible for the probing of capes
at the well defined I2C address for capes, parsing the EEPROM
info and matching them to specific cape drivers.
On top of that, a
Introducing capebus; a bus that allows small boards (capes) to connect
to a complex SoC using simple expansion connectors.
Up to now to support these kind of boards, one had to hack the board files,
and do all sort of gymnastics to handle all the different cases of
conflict resolution.
Capebus pr
Capebus is created to address the problem of many SoCs that can provide a
multitude of hardware interfaces but in order to keep costs down the main
boards only support a limited number of them. The rest are typically brought
out to pin connectors on to which other boards, named capes are connected
On Fri, Nov 2, 2012 at 12:32 PM, Pantelis Antoniou
wrote:
> The i2c2 alias cannot be resolved at compile time; there has to be
>
> a) A DT object format where unresolved aliases (symbols) are tracked
> b) A runtime DT linker that will resolve the alias, and will insert the
>i2c2-devices child
On Fri, Nov 2, 2012 at 8:43 AM, Pantelis Antoniou
wrote:
> Assuming that we do work on a DT object format, and that the runtime
> resolution mechanism is approved,
> then I agree that this part of the capebus patches can be dropped and the
> functionality assumed by generic
> DT core.
>
> The qu
linux,mtd-name allow to specify the mtd name for retro capability with
physmap-flash drivers as boot loader pass the mtd partition via the old
device name physmap-flash.
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD
---
Documentation/devicetree/bindings/mtd/mtd-physmap.txt |3 +++
drivers/
If no pinctrl available just report a warning as some architecture may not
need to do anything.
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD
Cc: Nicolas Ferre
Cc: Joachim Eastwood
Cc: net...@vger.kernel.org
---
drivers/net/ethernet/cadence/at91_ether.c | 11 +++
1 file changed, 11
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD
Cc: Nicolas Ferre
Cc: Joachim Eastwood
Cc: net...@vger.kernel.org
---
.../devicetree/bindings/net/cdns-emac.txt | 23 +++
drivers/net/ethernet/cadence/at91_ether.c | 72 ++--
2 files changed, 88 insertions
On Wed, Oct 31, 2012 at 10:04 AM, Alex Courbot wrote:
> Would anyone be opposed to having a gpio_get() function that works similarly
> to e.g. regulator_get() and clk_get()?
I understand the concept and why you want to do this.
However I think the global GPIO numberspace defeats the
purpose.
g
On Tue, Oct 30, 2012 at 3:12 PM, AnilKumar, Chimata wrote:
> I completely understood this named modes, I have added named
> modes like this in am335x-xxx.dts files
I do not understand how the pinctrl-single dts files work actually,
so please get Tony to review this part.
> I think "pinctrl-1" s
Hi!
On Fri, Nov 02, 2012 at 10:49:47PM +0530, Leela Krishna Amudala wrote:
> Hello Steffen,
>
> On Wed, Oct 31, 2012 at 2:58 PM, Steffen Trumtrar
> > +static int parse_property(struct device_node *np, char *name,
> > + struct timing_entry *result)
> > +{
> > +
On Thu, Nov 01, 2012 at 09:15:10PM +0100, Thierry Reding wrote:
> On Wed, Oct 31, 2012 at 10:28:02AM +0100, Steffen Trumtrar wrote:
> [...]
> > diff --git a/Documentation/devicetree/bindings/video/display-timings.txt
> > b/Documentation/devicetree/bindings/video/display-timings.txt
> [...]
> > @@
On Thu, Nov 01, 2012 at 09:08:42PM +0100, Thierry Reding wrote:
> On Wed, Oct 31, 2012 at 10:28:01AM +0100, Steffen Trumtrar wrote:
> [...]
> > +void timings_release(struct display_timings *disp)
> > +{
> > + int i;
> > +
> > + for (i = 0; i < disp->num_timings; i++)
> > + kfree(disp-
Hi,
This patch serie add dt and pinctrl support to the at91 ether
this is need to use the network on at91rm9200 as we now have dt
support on it
Jean-Christophe PLAGNIOL-VILLARD (2):
net: at91_ether: add dt support
net: at91_ether: add pinctrl support
Documen
On 11/02/2012 11:21 AM, Murali Karicheri wrote:
> This is a platform driver for asynchronous external memory interface
> available on TI SoCs. This driver was previously located inside the
> mach-davinci folder. As this DaVinci IP is re-used across multiple
> family of devices such as c6x, keystone
72 matches
Mail list logo
