> On Thursday 18 July 2013 02:56 PM, Nishanth Menon wrote:
>
> Since the cross-bar is not limited t0 IRQ lines and applicable for
> DMA request lines as well, making it IRQ chip doesn't make sense. Its
> not typical pin control functionality either but at least that framework
> is much closer to c
* Grygorii Strashko [130718 02:01]:
> On 07/18/2013 11:09 AM, Tony Lindgren wrote:
>
> Don't think it's debug code - IO chain need to be rearmed after each
> PRCM IO IRQ - otherwise IO wakeup events may be lost (at least on
> OMAP4, OMAP5 requires more complex handling((
* Grygorii Strashko [130717 10:11]:
> On 07/17/2013 06:38 PM, Tony Lindgren wrote:
> >* Grygorii Strashko [130717 04:49]:
> >>Before switching to DT pinctrl states of OMAP IPs have been handled by hwmod
> >>framework. After switching to DT-boot the pinctrl handling
* Grygorii Strashko [130717 09:48]:
> Hi,
>
> On 07/17/2013 06:32 PM, Tony Lindgren wrote:
> >* Grygorii Strashko [130717 04:49]:
> >>Add dynamic "active"/"idle" pin states for uart3/4 which will be applied
> >>when uart3/4 state is switc
s will stop working for
USB unless we do it like this so:
Acked-by: Tony Lindgren
> ---
> Documentation/devicetree/bindings/usb/omap-usb.txt |5 +
> Documentation/devicetree/bindings/usb/usb-phy.txt |6 ++
> arch/arm/boot/dts/omap3-beagle-xm.dts |
> + if (cpu_is_omap34xx())
> + musb_plat.phy_label = "twl4030";
> +
> if (soc_is_am35xx()) {
> oh_name = "am35x_otg_hs";
> name = "musb-am35x";
I don't think there's a USB PHY on non-twl4
* Grygorii Strashko [130717 04:49]:
> The pinctrl support in Device core assumed to be optional - so, It's
> valid case, when there are no definition for default device's pinctrl
> states in DT at all ("default", "active", "idle", "sleep").
> And in this case dev->pins == NULL and pinctrl_pm_selec
* Grygorii Strashko [130717 04:49]:
> Before switching to DT pinctrl states of OMAP IPs have been handled by hwmod
> framework. After switching to DT-boot the pinctrl handling was dropped from
> hwmod framework and, as it was recommended, OMAP IP's drivers have to be
> updated
> to handle pinctrl
* Grygorii Strashko [130717 04:49]:
> Add dynamic "active"/"idle" pin states for uart3/4 which will be applied
> when uart3/4 state is switched from active to idle and back by Runtime
> PM or during system suspend.
This is good for testing code, but should not be merged because
omap4 has the iopa
* Roger Quadros [130716 06:45]:
> On 07/16/2013 03:32 PM, Tony Lindgren wrote:
> > * Roger Quadros [130715 07:11]:
> >> Hi Tony,
> >>
> >> On 06/18/2013 07:04 PM, Roger Quadros wrote:
> >>> Till the OMAP clocks are correctly defined in device tree
* Roger Quadros [130715 07:11]:
> Hi Tony,
>
> On 06/18/2013 07:04 PM, Roger Quadros wrote:
> > Till the OMAP clocks are correctly defined in device tree, use
> > this temporary hack to provide clock alias to the USB PHY clocks.
> >
> > Without this, USB Host & Ethernet will not be functional wi
* Joel Fernandes [130626 20:48]:
> Build EDMA in by default to avoid fewer people stepping on their toes
> with broken DMA on drivers needing EDMA.
Thanks applying this one into omap-for-v3.11/fixes.
Tony
___
devicetree-discuss mailing list
devicetree-
quency instead. Also add a
> > > boolean to specify whether the clock is XTAL or not.
> > >
> > > Change all board files to reflect this.
> > >
> > > Cc: Tony Lindgren
> > > Cc: Sekhar Nori
> > > Signed-off-by: Luciano Coelho
> > >
* Bryan Wu [130701 12:12]:
> On Thu, Jun 27, 2013 at 7:24 AM, Tony Lindgren wrote:
> > * Tony Lindgren [130627 00:28]:
> >> * Bryan Wu [130626 16:53]:
> >> > On Wed, Jun 26, 2013 at 7:17 AM, Tony Lindgren wrote:
> >> > > @@ -22,6 +2
* Tony Lindgren [130627 00:28]:
> * Bryan Wu [130626 16:53]:
> > On Wed, Jun 26, 2013 at 7:17 AM, Tony Lindgren wrote:
> > > @@ -22,6 +22,7 @@
> > > #include
> > > #include
> > > #include
> > > +#include
> > > #include
* Bryan Wu [130626 16:53]:
> On Wed, Jun 26, 2013 at 7:17 AM, Tony Lindgren wrote:
> > @@ -22,6 +22,7 @@
> > #include
> > #include
> > #include
> > +#include
> > #include
> >
> > /* LED select registers determine the source that drive
Similar to tca6507, we can just parse the standard LED
properties for pca9633.
Tested on a pca9632, which is compatible with pca9633.
Signed-off-by: Tony Lindgren
--- /dev/null
+++ b/Documentation/devicetree/bindings/leds/pca9633.txt
@@ -0,0 +1,42 @@
+LEDs connected to pca9633 or pca9632
* Luciano Coelho [130626 01:19]:
> Hi Tony,
>
> On Tue, 2013-06-25 at 23:24 -0700, Tony Lindgren wrote:
> > * Luciano Coelho [130625 12:43]:
> > > On Tue, 2013-06-25 at 11:35 +0300, Luciano Coelho wrote:
> > > > Add device tree bindings documentation for the
* Dan Murphy [130625 07:13]:
> On 06/25/2013 06:32 AM, Ruslan Bilovol wrote:
> >The OMAP4 Blaze Tablet is TI OMAP4 processor-based
> >development platform in a tablet formfactor.
> >The platform contains many of the features found in
> >present-day handsets (such as audio, video, wireless
> >funct
* Luciano Coelho [130625 12:43]:
> (oh crap, now *really* fixed the ARM mailing list address)
>
> On Tue, 2013-06-25 at 11:35 +0300, Luciano Coelho wrote:
> > Add device tree bindings documentation for the TI WiLink modules.
> > Currently only the WLAN part of the WiLink6, WiLink7 and WiLink8
> >
* Benoit Cousson [130624 07:42]:
> Hi Tony,
>
> On 06/24/2013 12:19 PM, Tony Lindgren wrote:
> > Hi,
> >
> > For merging this series, I suggest the following sets:
> >
> > * Joel A Fernandes [130620 14:13]:
> >>
> >> Joel A Fernandes
Hi,
For merging this series, I suggest the following sets:
* Joel A Fernandes [130620 14:13]:
>
> Joel A Fernandes (3):
> edma: config: Enable config options for EDMA
> da8xx: config: Enable MMC and FS options
> ARM: davinci: Fix compiler warnings in devices-da8xx
>
> Matt Porter (8):
>
to be taken by Tony.
Sekhar, please go ahead and take this one. I'll reply
to the header email of this series how it should be
queued.
For the mach-omap2/Kconfig change:
Acked-by: Tony Lindgren
> > ---
> > arch/arm/mach-omap2/Kconfig |1 +
> > drivers/dma/Kconfig
* Tero Kristo [130624 00:51]:
> On 06/21/2013 10:25 AM, Tony Lindgren wrote:
> >* Tero Kristo [130619 06:25]:
> >>Now that the OMAP4 PRCM clock data has been converted to device tree
> >>representation, it is no longer needed as static clock data. OMAP4
> >>c
* Tero Kristo [130619 06:25]:
> Some of the clock.h contents are needed by the new OMAP clock driver,
> including dpll_data and clk_hw_omap. Thus, move these to the generic
> omap header file which can be accessed by the driver.
Do you mean "are only needed by the new OMAP clock driver"?
Otherwi
* Tero Kristo [130619 06:25]:
> Now that the OMAP4 PRCM clock data has been converted to device tree
> representation, it is no longer needed as static clock data. OMAP4
> clock init routine is also changed to register DT clocks first.
>
> Signed-off-by: Tero Kristo
> ---
> arch/arm/mach-omap2/
* Benoit Cousson [130619 05:41]:
> Hi Tony,
>
> On 06/19/2013 07:27 AM, Tony Lindgren wrote:
> >* Benoit Cousson [130619 03:17]:
> >>On 06/19/2013 02:46 AM, Tony Lindgren wrote:
> >>>
> >>>We have a similar issue with the MMC1 PBIAS. I think in t
* Benoit Cousson [130619 05:30]:
> On 06/19/2013 07:05 AM, Florian Vaussard wrote:
> >>>+
> >>>+/* HS USB Port 1 RESET */
> >>>+hsusb1_reset: hsusb1_reset_reg {
> >>>+compatible = "regulator-fixed";
> >>>+regulator-name = "hsusb1_reset";
> >>>+
* Benoit Cousson [130619 03:17]:
> On 06/19/2013 02:46 AM, Tony Lindgren wrote:
> >
> >We have a similar issue with the MMC1 PBIAS. I think in the long run we
> >should expand regulator (and possibly pinctrl) framework(s) to handle
> >comparators. We could just assu
* Roger Quadros [130619 00:42]:
> Hi Benoit,
>
> On 06/19/2013 04:17 AM, Benoit Cousson wrote:
> > Hi Roger,
> >
> > On 06/18/2013 11:04 AM, Roger Quadros wrote:
> >> Provide the RESET and Power regulators for the USB PHY,
> >> the USB Host port mode and the PHY device.
> >>
> >> Also provide pi
* Roger Quadros [130618 04:17]:
> Till the OMAP clocks are correctly defined in device tree, use
> this temporary hack to provide clock alias to the USB PHY clocks.
>
> Without this, USB Host & Ethernet will not be functional with
> device tree boots on Panda and uEVM.
Thanks, this looks OK to m
* Linus Walleij [130617 09:14]:
> On Mon, Jun 17, 2013 at 2:03 PM, Tony Lindgren wrote:
> > * Linus Walleij [130617 04:38]:
> >> On Fri, May 31, 2013 at 12:13 PM, Hebbar Gururaja
> >> wrote:
> >>
> >> > Make pinctrl-single able to handle sus
pinctrl-single.. But the patch seems fine to me:
Acked-by: Tony Lindgren
___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
* Felipe Balbi [130615 08:12]:
>
> fair enough, then let's just add those interrupts to hwmod which will,
> eventually, let us drop all of that data from hwmod.
Nope, we're already dropping the duplicate data from hwmod for
am33xx and omap4. See omap-for-v3.11/cleanup branch.
Regards,
Tony
___
* Linus Walleij [130613 08:35]:
> On Thu, Jun 13, 2013 at 4:41 PM, Balaji T K wrote:
>
> > You mean regulator via pinctrl APIs, I think It will just move the code
> > from omap_hsmmc to a new regulator file with it own init data for pinctrl.
>
> No I'm not saying you should use pinctrl as a "ba
* Mohammed, Afzal [130613 03:08]:
> Hi Tony,
>
> On Thu, Jun 13, 2013 at 15:24:54, Tony Lindgren wrote:
> > * Mohammed, Afzal [130613 00:04]:
>
> > > Patch 10 "ARM: OMAP2+: AM43x: basic dt support" is missing in
> > > omap-for-v3.11/soc branch a
* Mohammed, Afzal [130613 00:04]:
> Hi Tony,
>
> On Wed, Jun 12, 2013 at 22:42:00, Tony Lindgren wrote:
>
> > I've updated this patch to remove the "default y" and
> > "depends on ARCH_OMAP2PLUS" entries for the usual reasons
> > an
* Linus Walleij [130613 02:42]:
> On Thu, Jun 6, 2013 at 9:14 PM, Balaji T K wrote:
>
> > PBIAS register configuration is based on the regulator voltage
> > which supplies these pbias cells, sd i/o pads.
> > With PBIAS register address and bit definitions different across
> > omap[3,4,5], Simpli
* Balaji T K [130612 10:50]:
> On Wednesday 12 June 2013 08:05 PM, Tony Lindgren wrote:
> >* Balaji T K [130606 12:20]:
> >>add pbias states for pbias 0, 1.8V, 3V
> >>add omap3 sd/mmc2 loop back clock config for devconf1 in mmc2_init pinctrl
> >>state
>
* Balaji T K [130612 10:14]:
> On Wednesday 12 June 2013 08:05 PM, Tony Lindgren wrote:
> >* Balaji T K [130606 12:20]:
> >>omap3_pmx_core: padconf register are in two banks 0x48003000 to 0x48002268
> >>and 0x480025c0 to 0x480025f8.
> >>
> >>split om
* Afzal Mohammed [130527 07:42]:
> --- a/arch/arm/mach-omap2/io.c
> +++ b/arch/arm/mach-omap2/io.c
> @@ -586,6 +586,20 @@ void __init am33xx_init_early(void)
> }
> #endif
>
> +#ifdef CONFIG_SOC_AM43XX
> +void __init am43xx_init_early(void)
> +{
> + omap2_set_globals_tap(AM335X_CLASS,
> +
* Afzal Mohammed [130527 07:41]:
> --- a/arch/arm/mach-omap2/Kconfig
> +++ b/arch/arm/mach-omap2/Kconfig
> @@ -149,6 +149,16 @@ config SOC_AM33XX
> select MULTI_IRQ_HANDLER
> select COMMON_CLK
>
> +config SOC_AM43XX
> + bool "TI AM43x"
> + depends on ARCH_OMAP2PLUS
> + de
* Balaji T K [130606 12:20]:
> omap3_pmx_core: padconf register are in two banks 0x48003000 to 0x48002268
> and 0x480025c0 to 0x480025f8.
>
> split omap3_pmx_core into 2 banks as register between 0x48002270 and
> 0x48002564
> belongs to type pinctrl-single,bit-per-mux with access to certain bit
* Balaji T K [130612 07:39]:
> On Wednesday 12 June 2013 07:55 PM, Tony Lindgren wrote:
> >* Balaji T K [130606 12:20]:
> >>handle vcc and vcc_aux independently
> >>
> >>Signed-off-by: Balaji T K
> >>---
> >> drivers/mmc/host/omap_hsmmc.
* Balaji T K [130606 12:20]:
> PBIAS register configuration is based on the regulator voltage
> which supplies these pbias cells, sd i/o pads.
> With PBIAS register address and bit definitions different across
> omap[3,4,5], Simplify PBIAS configuration under three different
> regulator voltage le
* Balaji T K [130606 12:20]:
> add pbias states for pbias 0, 1.8V, 3V
> add sd/mmc1 pull strength values for control_mmc1 in mmc_init pinctrl state
This too should be under mmc1 in the omap4.dtsi file.
Tony
> Signed-off-by: Balaji T K
> ---
> arch/arm/boot/dts/omap4-panda-common.dtsi | 34
* Balaji T K [130606 12:20]:
> add pbias states for pbias 0, 1.8V, 3V
> add omap3 sd/mmc2 loop back clock config for devconf1 in mmc2_init pinctrl
> state
> add OMAP3430 sd/mmc1 loop back clock config for devconf0 in mmc1_init pinctrl
> state
> add OMAP3630 sd/mmc1 speed mode config for prog_io1
* Balaji T K [130606 12:20]:
> handle vcc and vcc_aux independently
>
> Signed-off-by: Balaji T K
> ---
> drivers/mmc/host/omap_hsmmc.c |9 +
> 1 files changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c
> index 18
* Balaji T K [130606 12:20]:
> Add needs_vmmc and needs_vmmc_aux to indicate whether regulator is
> applicable so that omap_hsmmc can handle deferred probe error
> properly for regulators.
> Remove the assumption that vmmc_aux regulator to be available only if vmmc is
> present. Platforms can have
* Roger Quadros [130611 05:57]:
> On 06/10/2013 06:21 PM, Tony Lindgren wrote:
> > * Quadros, Roger [130610 03:09]:
> >> +
> >> +static int __init pcs_omap_init(void)
> >> +{
> >> + platform_driver_register(&pcs_omap_soc_driver);
>
mask
>
> Would you like to sync with his style?
Thanks for catching that, yes that's how it should be now. Updated
patch below.
Regards,
Tony
From: Tony Lindgren
Date: Sat, 8 Jun 2013 08:40:35 -0700
Subject: [PATCH] pinctrl: single: Add hardware specific hooks for IRQ and GPI
* Tony Lindgren [130607 13:58]:
> * Tony Lindgren [130607 13:56]:
> > Now pinctrl-single-omap can handle the wake-up events for us now
> > as long as the events are configured in the .dts files.
>
> This patch I should queue separately, the rest should go via
> the pi
* Quadros, Roger [130610 03:09]:
> +
> +static int __init pcs_omap_init(void)
> +{
> + platform_driver_register(&pcs_omap_soc_driver);
> + platform_driver_register(&pcs_omap_driver);
> +
> + return 0;
> +}
> +module_init(pcs_omap_init);
>
> It seems this has to be moved to an ea
* Quadros, Roger [130610 05:37]:
> Hi Tony, (sorry, on Outlook web)
>
> - compatible = "ti,omap4-padconf", "pinctrl-single";
> + compatible = "ti,omap4-padconf";
>
> This change is not necessary if we make sure the pinctrl-single-omap driver
> gets reg
: Roger Quadros
Signed-off-by: Tony Lindgren
---
Here's a version of against current Linux next to as also the
Makefile entry for sirf had changed.
diff --git a/drivers/pinctrl/Makefile b/drivers/pinctrl/Makefile
index 3b26e3c..d4c2214 100644
--- a/drivers/pinctrl/Makefile
+++ b/drivers/pi
he pinctrl tree. Here's a version of this one against current
Linux next + Manjunathappa's patches.
Regards,
Tony
From: Tony Lindgren
Date: Sat, 8 Jun 2013 08:03:07 -0700
Subject: [PATCH] pinctrl: single: Prepare for supporting SoC specific features
Let's replace is_pinconf wit
* Benoit Cousson [130603 07:42]:
> Hi Tony,
>
> Please pull three DTS fixes for the next -rc.
Thanks pulling into omap-for-v3.10/fixes.
Regards,
Tony
> The following changes since commit d683b96b072dc4680fc74964eca77e6a23d1fa6e:
> Linus Torvalds (1):
> Linux 3.10-rc4
>
> are avail
* Tony Lindgren [130607 13:56]:
> Now pinctrl-single-omap can handle the wake-up events for us now
> as long as the events are configured in the .dts files.
This patch I should queue separately, the rest should go via
the pinctrl tree.
Regards,
Now pinctrl-single-omap can handle the wake-up events for us now
as long as the events are configured in the .dts files.
Done in collaboration with Roger Quadros .
Cc: Haojian Zhuang
Cc: Peter Ujfalusi
Cc: devicetree-discuss@lists.ozlabs.org
Signed-off-by: Roger Quadros
Signed-off-by: Tony
: Roger Quadros
Signed-off-by: Tony Lindgren
---
drivers/pinctrl/Makefile |3
drivers/pinctrl/pinctrl-single-omap.c | 287 +
include/linux/platform_data/pinctrl-single-omap.h |4
3 files changed, 293 insertions(+), 1 deletion
e is registered for the enable and disable
calls.
Done in collaboration with Roger Quadros .
Cc: Haojian Zhuang
Cc: Peter Ujfalusi
Cc: devicetree-discuss@lists.ozlabs.org
Signed-off-by: Roger Quadros
Signed-off-by: Tony Lindgren
---
.../devicetree/bindings/pinctrl/pinctrl-single.txt |5 +
ian Zhuang
Cc: Peter Ujfalusi
Cc: devicetree-discuss@lists.ozlabs.org
Signed-off-by: Roger Quadros
Signed-off-by: Tony Lindgren
---
drivers/pinctrl/pinctrl-single.c | 53 +++---
drivers/pinctrl/pinctrl-single.h | 15 +++
2 files changed, 52 inserti
igned-off-by: Manjunathappa, Prakash
> > ---
>
> Acked-by: Haojian Zhuang
Acked-by: Tony Lindgren
___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
ctions based sub mask.
Thanks for fixing this! Looks good to me, and things keep
working for me just fine with these applied:
Acked-by: Tony Lindgren
___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
* Mugunthan V N [130530 01:14]:
> On 5/28/2013 7:35 PM, Mugunthan V N wrote:
> >On 5/28/2013 3:06 AM, Tony Lindgren wrote:
> >>* Mugunthan V N [130526 11:28]:
> >>>From: Hebbar Gururaja
> >>>
> >>>Amend cpsw controller to optionally take a
* Wei Yongjun [130604 19:10]:
> From: Wei Yongjun
>
> The dereference to 'up' should be moved below the NULL test.
> Introduced by commit ddd85e225c8885b5e4419b0499ab27100e7c366a
> (serial: omap: prevent runtime PM for "no_console_suspend")
Acked-by: To
* Mike Turquette [130604 11:40]:
> Quoting Tony Lindgren (2013-06-04 07:55:43)
> > * Mike Turquette [130603 23:45]:
> > > This is a first pass at creating a unique node for each clock in the
> > > OMAP4 power, reset and & clock manager (PRCM). So far I have
* Mike Turquette [130603 23:45]:
> This is a first pass at creating a unique node for each clock in the
> OMAP4 power, reset and & clock manager (PRCM). So far I have only
> converted mux clocks & fixed-rate clocks, which coexist with the current
> clock data in the kernel. The rest needs to be
* Mike Turquette [130603 23:45]:
> Parses OMAP clock data from DT and registers those clocks with the clock
> framework. dt_omap_clk_init must be called early during boot for timer
> initialization so it is exported and called from the existing clock code
> instead of probing like a real driver.
* Hebbar Gururaja [130531 03:19]:
> Amend the hsmmc controller to optionally take a pin control handle and
> set the state of the pins to:
>
> - "default" on boot, resume and before performing a mmc transfer
> - "idle" after initial default, after resume default, and after each
> mmc/sd card acce
* Andreas Fenkart [130531 01:05]:
> Hi,
>
> this email adress will soon expire,
> my alternate email adress is
OK, noticed that the SDIO wake behaves in a different way between
wl12xx and mwifiex, and there's an issue with the muxing still for
legacy non-SDIO booting. So at least one more update
* Aaro Koskinen [130529 14:02]:
> Hi,
>
> On Thu, May 23, 2013 at 09:22:04AM +0200, Benoit Cousson wrote:
> > On 05/22/2013 09:44 PM, Aaro Koskinen wrote:
> > > Add minimal DT support for Nokia N950 & N9. The basic boot works. I can
> > > connect to both devices with USB networking & ssh. dmesg o
* Mugunthan V N [130526 11:28]:
> From: Hebbar Gururaja
>
> Amend cpsw controller to optionally take a pin control handle and set
> the state of the pins to:
>
> - "default" on boot, resume
> - "sleep" on suspend()
>
> This should make it possible to optimize energy usage for the pins
> for th
* Tony Lindgren [130520 19:55]:
> * Tony Lindgren [130520 14:03]:
> > * Andreas Fenkart [130515 01:51]:
> > > Without functional clock the omap_hsmmc module can't forward SDIO IRQs to
> > > the system. This patch reconfigures dat1 line as a gpio while the fcl
* Florian Vaussard [130523 08:42]:
> --- a/arch/arm/boot/dts/omap3-beagle-xm.dts
> +++ b/arch/arm/boot/dts/omap3-beagle-xm.dts
> @@ -29,13 +29,13 @@
>
> heartbeat {
> label = "beagleboard::usr0";
> - gpios = <&gpio5 22 0>; /* 150 -> D6 LED
* Florian Vaussard [130523 08:42]:
> index f39b237..b3cc896 100644
> --- a/arch/arm/boot/dts/omap2.dtsi
> +++ b/arch/arm/boot/dts/omap2.dtsi
> @@ -9,6 +9,7 @@
> */
>
> #include
> +#include
>
> #include "skeleton.dtsi"
>
> diff --git a/arch/arm/boot/dts/omap3-beagle.dts
> b/arch/arm/bo
* Florian Vaussard [130522 07:33]:
> Replace /include/ by #include for OMAP2+ DT, in order to use the
> C pre-processor, making use of #define features possible.
This is good, but let's use it with case. Probably the best use
for this right now is to add defines for the mux modes from
mach-omap2/
* Florian Vaussard [130522 07:33]:
> On OMAP3, the INTC interrupt controller has only 1 cell.
>
> Signed-off-by: Florian Vaussard
Thanks a similar fix is already queued up and on it's way to mainline
tree.
Regards,
Tony
> ---
> arch/arm/boot/dts/omap3.dtsi |2 +-
> 1 files changed, 1 in
* Stephen Warren [130522 08:32]:
> On 05/22/2013 08:27 AM, Florian Vaussard wrote:
> > Define the OMAP_GPIO macro to conveniently use GPIO inside OMAP DT.
> > For example:
> >
> > gpios = <&gpio6 3 0>; /* GPIO 163 */
> >
> > can be replaced by
> >
> > gpios = OMAP_GPIO(163, 0);
>
> >
* Tony Lindgren [130520 14:03]:
> * Andreas Fenkart [130515 01:51]:
> > Without functional clock the omap_hsmmc module can't forward SDIO IRQs to
> > the system. This patch reconfigures dat1 line as a gpio while the fclk is
> > off. When the fclk is present it
* Andreas Fenkart [130515 01:51]:
> Without functional clock the omap_hsmmc module can't forward SDIO IRQs to
> the system. This patch reconfigures dat1 line as a gpio while the fclk is
> off. When the fclk is present it uses the standard SDIO IRQ detection of
> the module.
>
> The gpio irq is ma
* Jon Hunter [130430 07:16]:
> Commit 8c8a777 (ARM: OMAP2+: Add function to read GPMC settings from
> device-tree) added a device-tree property "gpmc,device-nand" to indicate
> is the GPMC child device is NAND. This commit should have updated the
> GPMC NAND documentation (Documentation/devicetree
* Mark Jackson [130423 05:28]:
> OMAP devices support various NAND transfer modes.
>
> Currently all device-tree definitions will use the default "prefetch
> polled" mode, so this patch enables the transfer mode to be specified
> in the device-tree.
>
> Signed-off-by: Mark Jackson
Thanks apply
* Dan Murphy [130509 11:13]:
>
> Can we cleanly append to omap4_pmx_core without overriding the whole node?
> I don't want to recreate the pmx_core node in the es file.
Yes that should work just fine.
Regards,
Tony
___
devicetree-discuss mailing list
* Gupta, Pekon [130502 02:49]:
> From: "Philip, Avinash"
>
> Add GPMC data node to AM33XX device tree file.
>
> Signed-off-by: Philip Avinash
> Acked-by: Peter Korsgaard
> Signed-off-by: Pekon Gupta
Thanks adding into omap-for-v3.10/dt-fixes.
Tony
> ---
> Changes in v2:
> - Change
* Jon Hunter [130430 06:59]:
> The following changes since commit aecb65a34a780cd07fbaa652cc5d640f13f3ed5f:
>
> Merge branch 'omap-gpmc-for-v3.10-take2' of
> git://github.com/jonhunter/linux into omap-for-v3.10/gpmc (2013-04-04
> 11:22:33 -0700)
>
> are available in the git repository at:
>
* Sekhar Nori [130429 22:11]:
>
> On 4/29/2013 1:25 PM, Gupta, Pekon wrote:
> > From: avinash philip
> >
> > NAND flash connected in am335x-evm on GPMC controller. This patch adds
> > device tree node in am3355-evm with GPMC contoller timing for NAND flash
> > interface, NAND partition table, E
* Dan Murphy [130418 11:35]:
> On 04/18/2013 04:30 AM, Vincent Stehlé wrote:
> >On 04/17/2013 10:16 PM, Dan Murphy wrote:
> >>The GPIO for LED D1 on the omap4-panda a1-a3 rev and the omap4-panda-es
> >>are different.
> >(..)
> >>diff --git a/arch/arm/boot/dts/omap4-panda-common.dtsi
> >>b/arch/ar
* Nishanth Menon [130426 10:44]:
> Hi,
> It seems that I have not been paying close attention to
> actual voltage value seen on scope to map it back to verify the validity
> of the voltage value. Even though I did verify[1] that voltage did scale to
> values in DT entries, the values in the case o
* Luciano Coelho [130426 06:29]:
> On Thu, 2013-04-25 at 20:52 -0700, Tony Lindgren wrote:
> > This is needed to get wl12xx working with device tree based
> > booting.
> >
> > Note that we claim the various GPIO inputs in the regulator
> > as the proper muxing is
* Koen Kooi [130426 02:39]:
>
> Op 26 apr. 2013, om 05:52 heeft Tony Lindgren het volgende
> geschreven:
>
> > Without WLAN we cannot switch omap4 to use device tree
> > only booting. This patch can be reverted when the
> > binding for wl12xx is added.
>
>
ze, see the the panda for
what's currently missing.
Cc: Luciano Coelho
Cc: Benoit Cousson
Cc: Rajendra Nayak
Cc: Ruslan Bilovol
Cc: devicetree-discuss@lists.ozlabs.org
Signed-off-by: Tony Lindgren
---
arch/arm/boot/dts/omap4-sdp.dts | 39 ++-
no_regulator_off_init which
is really not what we want as then wl12xx won't get powered
up and down which is needed for resetting it.
Cc: Luciano Coelho
Cc: Benoit Cousson
Cc: Rajendra Nayak
Cc: devicetree-discuss@lists.ozlabs.org
Signed-off-by: Tony Lindgren
---
arch/arm/boot/dts/omap4-
Without WLAN we cannot switch omap4 to use device tree
only booting. This patch can be reverted when the
binding for wl12xx is added.
Cc: Luciano Coelho
Cc: Benoit Cousson
Cc: Rajendra Nayak
Cc: devicetree-discuss@lists.ozlabs.org
Signed-off-by: Tony Lindgren
---
arch/arm/mach-omap2
* Roger Quadros [130422 00:15]:
> On 04/19/2013 06:43 PM, Tony Lindgren wrote:
> > * Roger Quadros [130419 03:02]:
> >> Hi Benoit/Tony
> >>
> >> I've consolidated all the USB host device tree patches for Panda and
> >> Beagles
> >>
* Peter Ujfalusi [130423 00:47]:
> On 04/16/2013 11:32 PM, Tony Lindgren wrote:
> > * Peter Ujfalusi [130415 01:30]:
> >> On 04/10/2013 10:34 PM, Tony Lindgren wrote:
> >>> Yeah how about just change the pintctrl-single,bits register
> >>> naming to be
* Roger Quadros [130419 03:02]:
> Hi Benoit/Tony
>
> I've consolidated all the USB host device tree patches for Panda and Beagles
> to one place and addressed Tony's comments.
>
> NOTE: patch 1 depends on OMAP clock binding introduced in
> https://lkml.org/lkml/2013/4/12/407
>
> v3:
> - updated
* Roger Quadros [130419 01:23]:
> On 04/18/2013 11:09 PM, Tony Lindgren wrote:
>
> > the naming should be mode0name.modename to be consistent. Here's
> > what I dumped out, please check and replace spaces with tabs:
> >
> >
* Roger Quadros [130415 01:53]:
> Provide the RESET and Power regulators for the USB PHY,
> the USB Host port mode and the PHY device.
>
> The USB PHY needs AUXCLK3 to operate. Provide this information
> as well.
>
> Also provide pin multiplexer information for the USB host
> pins.
>
> This pat
* Igor Grinberg [130417 05:31]:
> On 04/17/13 11:38, Roger Quadros wrote:
> > On 04/17/2013 10:56 AM, Igor Grinberg wrote:
> >> On 04/17/13 04:30, Robert Nelson wrote:
> >>> On Tue, Apr 16, 2013 at 7:52 PM, Tony Lindgren wrote:
> >>>> * Roger Quadros
1 - 100 of 449 matches
Mail list logo
