On Mon, Jan 21, 2013 at 11:47:12AM -0600, Matt Sealey wrote:
> > Yes, maybe the module reset part of the SRC should be implemented as a
> > proper device driver in drivers/reset. Then we could use the interrupt
> > functionality and WARN_ON(timeout), as you suggest.
>
> That would be ideal. Maybe
Hi Kukjin,
On Tue, Jan 22, 2013 at 10:36 AM, Kukjin Kim wrote:
> Felipe Balbi wrote:
>>
>> On Fri, Jan 18, 2013 at 03:10:13PM +0200, Felipe Balbi wrote:
>> > Hi,
>> >
>> > On Tue, Dec 18, 2012 at 09:09:40PM +0530, Vivek Gautam wrote:
>> > > This patch-set enables the samsung-usbphy driver on exy
Hi Kukjin,
On Tue, Jan 22, 2013 at 11:05 AM, Kukjin Kim wrote:
> Sylwester Nawrocki wrote:
>>
>> On 12/24/2012 09:13 AM, Vivek Gautam wrote:
>> These two changes look good to me. For both of them:
>>
>> Reviewed-by: Doug Anderson
>> >>>
>> >>> Well, I have another idea. Yes, I kn
On Mon, Jan 21, 2013 at 12:59:17PM -0800, Simon Glass wrote:
> Ignore any patch files that we find, since these are likely to be
> used when sending patches upstream.
>
> Signed-off-by: Simon Glass
Acked-by: David Gibson >da...@gibson.dropbear.id.au>
Not really related to this series at all, bu
On Mon, Jan 21, 2013 at 12:59:16PM -0800, Simon Glass wrote:
> The function that prints a property can be useful to other programs,
> so move it into util.
>
> Signed-off-by: Simon Glass
Straightforward enough.
Acked-by: David Gibson
--
David Gibson| I'll have my music ba
On Mon, Jan 21, 2013 at 12:59:15PM -0800, Simon Glass wrote:
> This commit which changed the behaviour of this function broke one
> of the tests. Also the comment should be updated to reflect its new
> behaviour.
>
> Signed-off-by: Simon Glass
Acked-by: David Gibson
Jon, please apply asap, reg
Sylwester Nawrocki wrote:
>
> On 12/24/2012 09:13 AM, Vivek Gautam wrote:
> These two changes look good to me. For both of them:
>
> Reviewed-by: Doug Anderson
> >>>
> >>> Well, I have another idea. Yes, I know, specific chip name should be
used.
> >> But
> >>> you know the specifi
Vivek Gautam wrote:
>
> Changes from v5:
> - Rebased on top of latest patches:
> usb: phy: samsung: Introducing usb phy driver for hsotg (v9)
> usb: phy: samsung: Add support to set pmu isolation (v6)
>As a result adding hostphy enable mask and hostphy register offsets
>to
Felipe Balbi wrote:
>
> On Fri, Jan 18, 2013 at 03:10:13PM +0200, Felipe Balbi wrote:
> > Hi,
> >
> > On Tue, Dec 18, 2012 at 09:09:40PM +0530, Vivek Gautam wrote:
> > > This patch-set enables the samsung-usbphy driver on exynos5250,
> > > which enables the support for USB2 type and USB3 type phys
On Mon, Jan 21, 2013 at 12:59:15PM +0200, Pantelis Antoniou wrote:
> Hi David
>
> On Jan 21, 2013, at 6:48 AM, David Gibson wrote:
>
> > On Fri, Jan 04, 2013 at 09:31:09PM +0200, Pantelis Antoniou wrote:
> >> Introduce support for dynamic device tree resolution.
> >> Using it, it is possible to p
On Fri, Jan 04, 2013 at 09:31:10PM +0200, Pantelis Antoniou wrote:
> Introduce DT overlay support.
> Using this functionality it is possible to dynamically overlay a part of
> the kernel's tree with another tree that's been dynamically loaded.
> It is also possible to remove node and properties.
>
Hi Thomas and Gregory,
On Mon, Jan 21, 2013 at 11:07:10PM +0100, Gregory CLEMENT wrote:
> On 01/21/2013 07:17 PM, Thomas Petazzoni wrote:
> >> + irq_set_percpu_devid(virq);
> >> + irq_set_chip_and_handler(virq, &armada_370_xp_irq_chip,
> >> + hand
On 01/21/2013 07:31 PM, Arnd Bergmann wrote:
> On Monday 21 January 2013, Gregory CLEMENT wrote:
>> @@ -1624,7 +1624,7 @@ config LOCAL_TIMERS
>> bool "Use local timer interrupts"
>> depends on SMP
>> default y
>> - select HAVE_ARM_TWD if (!ARCH_MSM_SCORPIONMP && !EXYNO
On Friday 18 January 2013, Maxime Ripard wrote:
> The Allwinner SoCs have an IP module that handle both the muxing and the
> GPIOs.
>
> This IP has 8 banks of 32 bits, with a number of pins actually useful
> for each of these banks varying from one to another, and depending on
> the SoC used on th
On Monday 21 January 2013, Gregory CLEMENT wrote:
> Hum, I am not sure they are different. From my point of view it is the same
> IP,
> but the one on Armada XP can use a 25MHz fix source clock. Apart from this,
> all the registers are the same. Moreover currently with this property we
> still ha
On Fri, Jan 18, 2013 at 10:30 PM, Maxime Ripard
wrote:
> The Allwinner SoCs have an IP module that handle both the muxing and the
> GPIOs.
>
> This IP has 8 banks of 32 bits, with a number of pins actually useful
> for each of these banks varying from one to another, and depending on
> the SoC use
On 01/21/2013 07:17 PM, Thomas Petazzoni wrote:
> Dear Gregory CLEMENT,
>
> Just some minor nitpicks below.
OK I will take them into account for the V2.
Thanks
>
> On Mon, 21 Jan 2013 18:53:57 +0100, Gregory CLEMENT wrote:
>
>> +if (hw < ARMADA_370_XP_MAX_PER_CPU_IRQS) {
>> +
>
> Unneede
On 01/21/2013 07:22 PM, Arnd Bergmann wrote:
> On Monday 21 January 2013, Gregory CLEMENT wrote:
>> +
>> +Required properties:
>> +- compatible: Should be "marvell,armada-370-xp-timer"
>> +- interrupts: Should contain the list of Global Timer interrupts and
>> + then local timer interrupts
>> +- r
> "Philip" == Philip Avinash writes:
Philip> From: "Philip, Avinash"
Philip> Add GPMC data node to AM33XX device tree file.
Philip> Signed-off-by: Philip Avinash
Philip> ---
Philip> arch/arm/boot/dts/am33xx.dtsi | 12
Philip> 1 file changed, 12 insertions(+)
Philip>
fdtgrep operates like a grep for device trees, working on binary .dtb
files.
fdtgrep can find nodes by name or compatible string. It can find properties
by name. Using a list of of nodes/properties/compatible strings to match,
fdtgrep creates either .dts text output containing just those matches,
Since fdtgrep does everything that fdtdump does now, perhaps we should
replace it with a symlink.
Signed-off-by: Simon Glass
---
Makefile |5 +-
fdtdump.c | 137 -
fdtgrep.c | 40 --
3 files changed, 30 insertion
Given a set of nodes and properties, find the regions of the device tree
which describe those parts.
A test is provided which builds a tree while tracking where the regions
should be, then calls fdt_find_regions() to make sure that it agrees.
Further tests will come as part of fdtgrep.
Signed-of
(We probably don't want this patch, and certainly can't apply it as is,
but I send it in order to find out the intent of fdt_string()).
At present fdt_string() says that returns:
- a pointer to the string, on success
- NULL, if stroffset is out of bounds
However it does not in fact return
This function is useful outside libfdt, so export it.
Signed-off-by: Simon Glass
---
libfdt/fdt_ro.c |5 ++---
libfdt/libfdt.h | 14 ++
2 files changed, 16 insertions(+), 3 deletions(-)
diff --git a/libfdt/fdt_ro.c b/libfdt/fdt_ro.c
index 42da2bd..50007f6 100644
--- a/libfdt/f
The function that prints a property can be useful to other programs,
so move it into util.
Signed-off-by: Simon Glass
---
fdtdump.c | 37 +
util.c| 37 +
util.h| 14 ++
3 files changed, 52 insertion
This commit which changed the behaviour of this function broke one
of the tests. Also the comment should be updated to reflect its new
behaviour.
Signed-off-by: Simon Glass
---
tests/run_tests.sh |4 +---
util.h |8 +---
2 files changed, 6 insertions(+), 6 deletions(-)
d
Ignore any patch files that we find, since these are likely to be
used when sending patches upstream.
Signed-off-by: Simon Glass
---
.gitignore |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/.gitignore b/.gitignore
index 7cabc49..545b899 100644
--- a/.gitignore
+++ b/.g
This series adds a new function, fdt_find_regions() which maps FDT parts
such as nodes and properties to their regions in the FDT binary. The
function is then used to implement a grep utility for FDTs.
The function itself is quite simple and small, but this series adds tests
and a grep utility, so
> "Philip" == Philip Avinash writes:
Philip> From: "Philip, Avinash"
Philip> Add ELM data node to AM33XX device tree file.
Philip> Signed-off-by: Philip Avinash
Philip> ---
Philip> arch/arm/boot/dts/am33xx.dtsi |8
Philip> 1 file changed, 8 insertions(+)
Philip> diff
On Monday 21 January 2013, Matt Sealey wrote:
> On Mon, Jan 21, 2013 at 12:31 PM, Arnd Bergmann wrote:
> > On Monday 21 January 2013, Gregory CLEMENT wrote:
> >> @@ -1624,7 +1624,7 @@ config LOCAL_TIMERS
> >> bool "Use local timer interrupts"
> >> depends on SMP
> >> defaul
On Mon, Jan 21, 2013 at 12:31 PM, Arnd Bergmann wrote:
> On Monday 21 January 2013, Gregory CLEMENT wrote:
>> @@ -1624,7 +1624,7 @@ config LOCAL_TIMERS
>> bool "Use local timer interrupts"
>> depends on SMP
>> default y
>> - select HAVE_ARM_TWD if (!ARCH_MSM_SCORPIONM
Quoting Tomasz Figa (2013-01-21 08:22:39)
> Hi Thomas, Sylwester,
>
> On Monday 21 of January 2013 15:29:16 Sylwester Nawrocki wrote:
> > On 12/30/2012 01:33 AM, Thomas Abraham wrote:
> > > Changes since v4:
> > > - Rebased to linux-3.8-rc1.
> > >
> > > Changes since v3:
> > > - Includes changes
On Mon, 21 Jan 2013 10:21:08 -0700, Stephen Warren
wrote:
> On 01/20/2013 06:22 PM, Thomas Abraham wrote:
>> Add an entry in __clksrc_of_table so that ARMv7 architected timer is
>> discoverable using call to clocksource_of_init.
>
>> diff --git a/arch/arm/kernel/arch_timer.c
b/arch/arm/kernel/arc
* Belisko Marek [121115 05:31]:
> CC'ing Tony
>
> On Thu, Nov 15, 2012 at 12:59 PM, Grant Likely
> wrote:
> > On Wed, 14 Nov 2012 21:26:58 +0100, Belisko Marek
> > wrote:
> >> CC' Grant & Rob
> >
> > Hi Marek
> >
> > Since this is an OMAP board, you should send the changes to Tony and
> > they
Hi Marc,
On 21 January 2013 05:46, Mark Rutland wrote:
> On Mon, Jan 21, 2013 at 10:02:18AM +, Thomas Abraham wrote:
>> Allow the MCT controller base address and interrupts to be obtained from
>> device tree and remove unused static definitions of these. The non-dt support
>> for Exynos5250 i
* Ezequiel Garcia [130121 09:00]:
> Hi Mark,
>
> On Mon, Jan 21, 2013 at 9:30 AM, Mark Rutland wrote:
> > [...]
> >
> >> diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-omap2/gpmc.c
> >> index 01ce462..f7de9eb 100644
> >> --- a/arch/arm/mach-omap2/gpmc.c
> >> +++ b/arch/arm/mach-omap2/gp
On Monday 21 January 2013, Gregory CLEMENT wrote:
> @@ -1624,7 +1624,7 @@ config LOCAL_TIMERS
> bool "Use local timer interrupts"
> depends on SMP
> default y
> - select HAVE_ARM_TWD if (!ARCH_MSM_SCORPIONMP && !EXYNOS4_MCT)
> + select HAVE_ARM_TWD if (!ARCH_MSM_
Hi Stephen,
On 21 January 2013 09:21, Stephen Warren wrote:
> On 01/20/2013 06:22 PM, Thomas Abraham wrote:
>> Add an entry in __clksrc_of_table so that ARMv7 architected timer is
>> discoverable using call to clocksource_of_init.
>
>> diff --git a/arch/arm/kernel/arch_timer.c b/arch/arm/kernel/a
On Monday 21 January 2013, Gregory CLEMENT wrote:
> +
> +Required properties:
> +- compatible: Should be "marvell,armada-370-xp-timer"
> +- interrupts: Should contain the list of Global Timer interrupts and
> + then local timer interrupts
> +- reg: Should contain location and length for timers reg
Hi Mark,
On 21 January 2013 04:13, Mark Rutland wrote:
> Hi Thomas,
>
> This looks really useful, and it's going to conflict with my arch_timer /
> arm_generic driver unification series [1].
>
> I'm happy to take this as part of my series if that's ok with you?
Sure, that's fine. This patch woul
Dear Gregory CLEMENT,
Just some minor nitpicks below.
On Mon, 21 Jan 2013 18:53:57 +0100, Gregory CLEMENT wrote:
> + if (hw < ARMADA_370_XP_MAX_PER_CPU_IRQS) {
> +
Unneeded empty line.
> + irq_set_percpu_devid(virq);
> + irq_set_chip_and_handler(virq, &armada_370_xp
On 01/21/2013 06:59 PM, Russell King - ARM Linux wrote:
> On Mon, Jan 21, 2013 at 06:53:58PM +0100, Gregory CLEMENT wrote:
>> +struct clock_event_device __percpu **percpu_armada_370_xp_evt;
>> +
>
> Have you run this through checkpatch? Should the above be static?
>
Yes (and it didn't complain)
On Mon, Jan 21, 2013 at 06:53:58PM +0100, Gregory CLEMENT wrote:
> +struct clock_event_device __percpu **percpu_armada_370_xp_evt;
> +
Have you run this through checkpatch? Should the above be static?
___
devicetree-discuss mailing list
devicetree-discu
Timer driver for Armada 370 and Armada XP have gained local timers
support. So it needs new resources information regarding the IRQs
and the registers.
Also move the documentation in the new and more accurate directory
Signed-off-by: Gregory CLEMENT
---
.../bindings/arm/armada-370-xp-timer.txt
Now that the time-armada-370-xp support local timers, updated the
device tree to take it into account.
Signed-off-by: Gregory CLEMENT
---
arch/arm/boot/dts/armada-370-xp.dtsi |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/armada-370-xp.dtsi
b/arch/
Now that we have support for local timers, enable it by default
Signed-off-by: Gregory CLEMENT
---
arch/arm/configs/mvebu_defconfig |1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/configs/mvebu_defconfig b/arch/arm/configs/mvebu_defconfig
index b5bc96c..28c1e38 100644
--- a/arch/a
The Armada 370 and Armada XP SoCs don't use the TWD timers, so don't
select it by default if CONFIG_LOCAL_TIMERS is selected
Signed-off-by: Gregory CLEMENT
---
arch/arm/Kconfig |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 67874b
On the SOCs Armada 370 and Armada XP, each CPU comes with two private
timers. This patch use the timer 0 of each CPU as local timer for the
clockevent if CONFIG_LOCAL_TIMER is selected. In the other case, use
only the private Timer 0 of CPU 0.
Signed-off-by: Gregory CLEMENT
---
drivers/clocksour
Hello,
The Armada XP SoCs comes with private timers. This allows us to use
local timers through CONFIG_LOCAL_TIMERS and as stated in the kconfig
help, it prevents a "thundering herd" at every timer tick.
Armada 370 also have these private timers, and even if it comes only
with a single CPU, the f
MPIC allows the use of private interrupt for each CPUs. The 28th first
interrupts are per-cpu. This patch adds support to use them.
Signed-off-by: Gregory CLEMENT
---
arch/arm/mach-mvebu/irq-armada-370-xp.c | 18 +-
1 file changed, 13 insertions(+), 5 deletions(-)
diff --git a
On Mon, Jan 21, 2013 at 3:52 AM, Philipp Zabel wrote:
> Hi Matt,
>
> thank you for your comments.
>
> Am Freitag, den 18.01.2013, 13:57 -0600 schrieb Matt Sealey:
>> On Wed, Jan 16, 2013 at 10:13 AM, Philipp Zabel
>> wrote:
>>
>> +
>> +static int imx_src_reset(unsigned long sw_reset_idx)
>> +{
>
On 01/20/2013 06:22 PM, Thomas Abraham wrote:
> Add an entry in __clksrc_of_table so that ARMv7 architected timer is
> discoverable using call to clocksource_of_init.
> diff --git a/arch/arm/kernel/arch_timer.c b/arch/arm/kernel/arch_timer.c
> +#ifdef CONFIG_CLKSRC_OF
> +CLOCKSOURCE_OF_DECLARE(ar
Hi Mark,
On Mon, Jan 21, 2013 at 9:30 AM, Mark Rutland wrote:
> [...]
>
>> diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-omap2/gpmc.c
>> index 01ce462..f7de9eb 100644
>> --- a/arch/arm/mach-omap2/gpmc.c
>> +++ b/arch/arm/mach-omap2/gpmc.c
>> @@ -39,6 +39,7 @@
>> #include "omap_device.h
Hi Thomas, Sylwester,
On Monday 21 of January 2013 15:29:16 Sylwester Nawrocki wrote:
> On 12/30/2012 01:33 AM, Thomas Abraham wrote:
> > Changes since v4:
> > - Rebased to linux-3.8-rc1.
> >
> > Changes since v3:
> > - Includes changes suggested by Tomasz Figa
> >
> > This patch series migrate
On 12/30/2012 01:33 AM, Thomas Abraham wrote:
> Changes since v4:
> - Rebased to linux-3.8-rc1.
>
> Changes since v3:
> - Includes changes suggested by Tomasz Figa
>
> This patch series migrates the Samsung Exynos4 SoC clock code to adopt the
> common clock framework. The use of Samsung specific
On Friday 18 of January 2013 14:30:21 Praveen Paneri wrote:
> Changes from v8:
> Resending this patch series after rebasing to the latest usb-next
> branch. Rewording inline comments for better readability.
> Removed IS_ENABLED(CONFIG_OF) as pdev->dev.of_node is enough to check
> for dt support. Us
Added has_mailbox to the musb platform data to specify that omap uses
an external mailbox (in control module) to communicate with the musb
core during device connect and disconnect.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/mach-omap2/usb-musb.c |3 +++
include/linux/usb/musb.h
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act in host mode or in device mode.
Writing to control module registers for doing the above task which was
previously done in omap glu
Start using the control module driver for powering on the PHY and for
writing to the mailbox instead of writing to the control module
registers on their own.
Signed-off-by: Kishon Vijay Abraham I
---
Documentation/devicetree/bindings/usb/omap-usb.txt |4 ++
Documentation/devicetree/bindings/
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act in host mode or in device mode.
Writing to control module registers for doing the above task which was
previously done in omap glu
A seperate driver has been added to handle the usb part of control
module. A device for the above driver is created here, using the register
address information to be used by the driver for powering on the PHY and
for writing to the mailbox.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/mac
On Mon, Jan 21, 2013 at 10:02:18AM +, Thomas Abraham wrote:
> Allow the MCT controller base address and interrupts to be obtained from
> device tree and remove unused static definitions of these. The non-dt support
> for Exynos5250 is removed but retained for Exynos4210 based platforms.
>
> Cc
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
---
drivers/usb/musb/omap2430.c |7 ++-
1 file changed, 6 inse
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
the phy on success, -EPROBE_DEFER if there is a
The non-dt probing allowed passing the location via platform data from
the beginning. So make up leeway for device tree probing.
Signed-off-by: Uwe Kleine-König
---
Hello,
I wonder if the location property should be mandatory. Do you have an
opinion?
BTW, I was surprised that I had to use of_p
[...]
> diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-omap2/gpmc.c
> index 01ce462..f7de9eb 100644
> --- a/arch/arm/mach-omap2/gpmc.c
> +++ b/arch/arm/mach-omap2/gpmc.c
> @@ -39,6 +39,7 @@
> #include "omap_device.h"
> #include "gpmc.h"
> #include "gpmc-nand.h"
> +#include "gpmc-onenan
Hi Thomas,
This looks really useful, and it's going to conflict with my arch_timer /
arm_generic driver unification series [1].
I'm happy to take this as part of my series if that's ok with you?
On Mon, Jan 21, 2013 at 01:22:06AM +, Thomas Abraham wrote:
> Add an entry in __clksrc_of_table s
Add display_timing structure and the according helper functions. This allows
the description of a display via its supported timing parameters.
Also, add helper functions to convert from display timings to a generic
videomode
structure.
The struct display_timing specifies all needed parameters to
The struct display_timing is specific to the via subsystem. The naming leads to
collisions with the new struct display_timing, which is supposed to be a shared
struct between different subsystems.
To clean this up, prepend the existing struct with the subsystem it is specific
to.
Signed-off-by: St
Add helper to get drm_display_mode from devicetree.
Signed-off-by: Steffen Trumtrar
Reviewed-by: Thierry Reding
Acked-by: Thierry Reding
Tested-by: Thierry Reding
Tested-by: Philipp Zabel
Reviewed-by: Laurent Pinchart
Acked-by: Laurent Pinchart
Tested-by: Afzal Mohammed
---
drivers/gpu/dr
This adds support for reading display timings from DT into a struct
display_timings. The of_display_timing implementation supports multiple
subnodes. All children are read into an array, that can be queried.
If no native mode is specified, the first subnode will be used.
For cases where the graph
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
- Exynos: smdk5250 by Leela
- AM335X EV
Add a function to convert from the generic videomode to a fb_videomode.
Signed-off-by: Steffen Trumtrar
Reviewed-by: Thierry Reding
Acked-by: Thierry Reding
Tested-by: Thierry Reding
Tested-by: Philipp Zabel
Reviewed-by: Laurent Pinchart
Acked-by: Laurent Pinchart
Tested-by: Afzal Mohammed
Add helper to get fb_videomode from devicetree.
Signed-off-by: Steffen Trumtrar
Reviewed-by: Thierry Reding
Acked-by: Thierry Reding
Tested-by: Thierry Reding
Tested-by: Philipp Zabel
Reviewed-by: Laurent Pinchart
Acked-by: Laurent Pinchart
Tested-by: Afzal Mohammed
---
drivers/video/fbmo
Add conversion from videomode to drm_display_mode
Signed-off-by: Steffen Trumtrar
Reviewed-by: Thierry Reding
Acked-by: Thierry Reding
Tested-by: Thierry Reding
Tested-by: Philipp Zabel
Reviewed-by: Laurent Pinchart
Acked-by: Laurent Pinchart
Tested-by: Afzal Mohammed
---
drivers/gpu/drm/
Hi David
On Jan 21, 2013, at 6:48 AM, David Gibson wrote:
> On Fri, Jan 04, 2013 at 09:31:09PM +0200, Pantelis Antoniou wrote:
>> Introduce support for dynamic device tree resolution.
>> Using it, it is possible to prepare a device tree that's
>> been loaded on runtime to be modified and inserted
None of mmc drivers implements bus-width as a required device tree
property. Instead, some drivers like atmel-mci, dw_mmc, sdhci-s3c
implement it as an optional one, and will force bus width to be 1
when the property is absent. Let's change the common binding to
reflect what the drivers are usual
Hi,
I'm trying to find a proper way for userspace to determine which
devices to talk to. Say you have 4 SPI devices that are registered
against spidev (the userspace SPI handling driver). The device tree
obviously knows which device is which (e.g. a temperature sensor, a
memory device, an actuator
On Friday 18 January 2013 09:23 PM, Rob Herring wrote:
> On 01/18/2013 06:24 AM, Vineet Gupta wrote:
>> This is minimal infrastructure needed for devicetree work.
>> It uses an a sample "skeleton" devicetree - embedded in kernel image -
>> to print the board, manufacturer by parsing the top-level "
Hi Kukjin,
On Fri, Jan 18, 2013 at 8:37 PM, Felipe Balbi wrote:
> On Fri, Jan 18, 2013 at 07:59:52PM +0530, Vivek Gautam wrote:
>> HI Balbi,
>>
>>
>> On Fri, Jan 18, 2013 at 7:52 PM, Felipe Balbi wrote:
>> > On Fri, Jan 18, 2013 at 07:51:08PM +0530, Vivek Gautam wrote:
>> >> Hi Felipe,
>> >>
>>
Move the multi core timer (mct) driver from mach-exynos to
drivers/clocksource and update the Kconfig and makefiles.
Signed-off-by: Thomas Abraham
---
arch/arm/Kconfig |2 +-
arch/arm/mach-exynos/Kconfig |6 --
arch/arm/mach-exy
With device tree support enabled for MCT controller, the staticio-remapping
of the MCT controller address space is removed for Exynos5 platforms (which
supports only device tree based boot).
Cc: Changhwan Youn
Signed-off-by: Thomas Abraham
---
arch/arm/mach-exynos/common.c |5
Add MCT device tree node for Exynos4210, Exynos4212, Exynos4412 and Exynos5250.
Cc: Changhwan Youn
Signed-off-by: Thomas Abraham
---
arch/arm/boot/dts/exynos4210.dtsi |7 +++
arch/arm/boot/dts/exynos4212.dtsi |9 +
arch/arm/boot/dts/exynos4412.dtsi |7 +++
arch/arm/b
Add entries to __clksrc_of_table so that Exynos MCT controller is discoverable
using call to clocksource_of_init. With this change, it would be appropriate to
rename the function 'exynos4_timer_init' as 'mct_init' since it aptly describes
this function. Additionally, the 'init_time' callback of all
Allow the MCT controller base address and interrupts to be obtained from
device tree and remove unused static definitions of these. The non-dt support
for Exynos5250 is removed but retained for Exynos4210 based platforms.
Cc: Changhwan Youn
Signed-off-by: Thomas Abraham
---
.../bindings/timer/s
Instead of using soc_is_xxx macro at more than one place in the MCT
controller driver to decide the MCT interrpt number to be setup, populate
a table of known MCT global and local timer interrupts and use the values
in table to setup the MCT interrupts.
This also helps in adding device tree suppor
All the MCT register read/writes use a fixed remapped address S5P_VA_SYSTIMER.
With device tree support for MCT controller, it is possible to remove the
static remap of the MCT controller address space and do the remap during the
initialization of the MCT controller with the physical address obtain
Changes since v3:
- Based on Stephen Warren's CONFIG_CLKSRC_OF patches (merged from arm-soc
'timer/cleanup' branch).
- Moved the mct driver from mach-exynos to drivers/clocksource
Changes since v2:
- Rebased to linux 3.8-rc1
Changes since v1:
- Includes changes suggested by Sylwester Nawrocki
Hi Matt,
thank you for your comments.
Am Freitag, den 18.01.2013, 13:57 -0600 schrieb Matt Sealey:
> On Wed, Jan 16, 2013 at 10:13 AM, Philipp Zabel
> wrote:
> > The SRC has auto-deasserting reset bits that control reset lines to
> > the GPU, VPU, IPU, and OpenVG IP modules. This patch adds a r
On Sun, Jan 20, 2013 at 12:51:57PM +, David Linares wrote:
>
> Hi guys,
>
> I have just signed up to this distribution list to try to get some
> support/understanding of an issue I am having when switching from
> kernel v3.7.3 to v3.8-rc1. I am using a Voipac i.MX25 and on v3.7.3,
> barebox
Hi,
On Mon, Jan 21, 2013 at 12:15:10PM +0530, Vivek Gautam wrote:
> Hi Felipe,
>
>
> On Mon, Jan 14, 2013 at 6:29 PM, Vivek Gautam
> wrote:
> > Changes from v2:
> > - Renaming 'samsung-usbphy.c' driver to 'samsung-usb2.c' indicating
> >usb 2.0 phy controller's driver for Samsung's SoCs.
>
91 matches
Mail list logo
