On Mon, 2013-02-18 at 20:13 -0800, Simon Glass wrote:
> On Sat, Feb 16, 2013 at 12:49 PM, Dmitry Torokhov
> > On Fri, Feb 15, 2013 at 08:16:12PM -0800, Simon Glass wrote:
> >> + for (row = 0; row < ckdev->rows; row++) {
> >> + if (cros_ec_keyb_row_has_ghosting(ckdev, buf, row))
> >>
On 02/18/2013 08:30 PM, Wei Ni wrote:
Using macros for the indexes and nrs of temp8 and temp11.
This make the code much clearer.
Signed-off-by: Wei Ni
Acked-by: Alexandre Courbot
Great patch. This makes the code much more readable. I also compiled
lm90.o before and after this patch, and di
On Thu, Feb 14, 2013 at 10:54:28AM -0700, Stephen Warren wrote:
> On 02/13/2013 11:38 PM, Hiroshi Doyu wrote:
> > To replace magic number in "clocks = <&tegra_car 28>;"
>
> I like the concept here; I was thinking about doing this today, but you
> beat me to it:-) Feel free to create the Tegra30 he
On 02/18/2013 08:30 PM, Wei Ni wrote:
Register the remote sensor to the thermal framework.
It can support to show the temperature and read/write threshold.
Signed-off-by: Wei Ni
---
arch/arm/boot/dts/tegra30-cardhu.dtsi |1 +
drivers/hwmon/lm90.c | 182 +
Hi,
On Mon, Feb 18, 2013 at 12:21 AM, Thomas Abraham
wrote:
> The clock frequency of xxti and xusbxti clocks is dependent on the frequency
> of the
> on-board oscillator that is used to generate these clocks. So allow the
> frequency
> of these clocks to be specfied from device tree.
>
> Cc: Ku
On Mon, Feb 18, 2013 at 2:25 PM, Sylwester Nawrocki
wrote:
> My context was a multiprocessor SoC, where one of the processors is somehow
> application specific (e.g. camera ISP) and can be considered as a slave
> subsystem, running it's firmware and sharing system memory with the main
> processor
Hi Dmitry,
On Sat, Feb 16, 2013 at 12:49 PM, Dmitry Torokhov
wrote:
> Hi Simon,
>
> On Fri, Feb 15, 2013 at 08:16:12PM -0800, Simon Glass wrote:
>> + for (row = 0; row < ckdev->rows; row++) {
>> + if (cros_ec_keyb_row_has_ghosting(ckdev, buf, row))
>> + return
On 02/18/2013 08:30 PM, Wei Ni wrote:
diff --git a/Documentation/devicetree/bindings/thermal/tegra3-thermal.txt
b/Documentation/devicetree/bindings/thermal/tegra3-thermal.txt
new file mode 100644
This should go with the previous patch (which introduces the driver)
instead of this one. Binding
On Mon, Feb 18, 2013 at 11:27:46PM +0300, Sergei Shtylyov wrote:
> Hello.
>
>Here's the v2 of the set of 4 patches against the Simon Horman's
> renesas.git
> repo, 'next' branch:
>
> [1/4] libata: add R-Car SATA driver
> [2/4] ARM: mach-shmobile: r8a7779: SATA DT configuration
> [3/4] ARM: m
On Mon, Feb 18, 2013 at 07:30:28PM +0800, Wei Ni wrote:
> Register the remote sensor to the thermal framework.
> It can support to show the temperature and read/write threshold.
>
> Signed-off-by: Wei Ni
> ---
> arch/arm/boot/dts/tegra30-cardhu.dtsi |1 +
> drivers/hwmon/lm90.c
On Mon, Feb 18, 2013 at 07:30:25PM +0800, Wei Ni wrote:
> Add support to handle irq. When the temperature touch the limit value, the
> driver can handle the interrupt.
>
> Signed-off-by: Alexandre Courbot
> Signed-off-by: Wei Ni
> ---
> drivers/hwmon/lm90.c | 38 ++
On Mon, Feb 18, 2013 at 07:30:24PM +0800, Wei Ni wrote:
> Split set&show temp codes as common functions, so we can use it directly when
> implement linux thermal framework.
>
> Signed-off-by: Wei Ni
> ---
> drivers/hwmon/lm90.c | 117
> +++---
> 1 fi
On 02/18/2013 08:30 PM, Wei Ni wrote:
Enable thermal sensor lm90 in the dts file.
Acked-by: Alexandre Courbot
Btw, shouldn't this patch come last, after all the changes you did to
lm90? If you keep the current order, you will need to ensure that the
device performs as expected on Cardhu for
On 01/28/2013 11:54 AM, Florian Vaussard wrote:
> Add device-tree support for the GPMC controller on the OMAP3.
>
> Signed-off-by: Florian Vaussard
> ---
> arch/arm/boot/dts/omap3.dtsi | 11 +++
> 1 files changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/boot/dts/om
On Mon, Feb 18, 2013 at 06:04:21PM +0400, Sergei Shtylyov wrote:
> Hello.
>
> On 18-02-2013 5:23, Simon Horman wrote:
>
> >>Here's the set of 4 patches against the Simon Horman's renesas.git
> >> repo, 'next' branch:
>
> >>[1/4] ARM: mach-shmobile: r8a7779: SATA DT configuration
> >>[2/4] A
On 02/15/2013 09:33 AM, Sascha Hauer wrote:
On Thu, Feb 14, 2013 at 11:08:54PM +0100, Sylwester Nawrocki wrote:
On 02/14/2013 10:30 PM, Sascha Hauer wrote:
On Thu, Feb 14, 2013 at 01:45:26PM +0100, Marek Szyprowski wrote:
...
Here is my initial proposal for device tree integration for Contigu
On Monday 18 February 2013, Guennadi Liakhovetski wrote:
> On Mon, 18 Feb 2013, Arnd Bergmann wrote:
>
> Sorry, I'm not sure how best to describe it, and I don't have sufficient
> information myself. In any case on a block-diagram of sh73a0 SDHI devices
> aren't directly connected to a common su
On 02/16/2013 11:18 PM, Nishanth Peethambaran wrote:
> Limiting the scope of the product to a particular use-case (720p or
> 1080p video playback) will be part of firmware mostly OTP-ed in the
> SoC. Firmware author could decide the amount of CMA memory needed and
> put this as part of DT.
What ke
Hi Fabio,
> Hi all,
> this patchset add the timeout-sec property to the watchdog core,
> to the at91sam9_wdt driver and on all framework enabled watchdog driver
> with dt support.
> The at91sam9_wdt is tested on evk-pr3,
> the other drivers are compile tested only.
>
> Hi Wim,
> because the first
On Fri, Feb 15, 2013 at 05:52:06PM +, Dave Martin wrote:
> On Fri, Feb 15, 2013 at 05:21:02PM +, Lorenzo Pieralisi wrote:
> > Hi all,
> >
> > in order to come up with a solid solution to the affinity bindings concept
> > we are facing in the ARM world, I am posting this RFC so that hopeful
Hi,
On Mon, Feb 18, 2013 at 05:08:16PM +0530, Afzal Mohammed wrote:
> + uart1: serial@44e09000 {
> + compatible = "ti,am4372-uart","ti,omap2-uart";
> + clock-frequency = <4800>;
> + reg = <0x44e09000 0x2000>;
> +
On Mon, 18 Feb 2013, Arnd Bergmann wrote:
> On Monday 18 February 2013, Guennadi Liakhovetski wrote:
> > > Also, should the barrier not be after the MMIO read, rather than before
> > > it?
> > > Typically the barrier should ensure that any read from memory after an
> > > MMIO read reflects the me
On Monday 18 February 2013, Guennadi Liakhovetski wrote:
> > Also, should the barrier not be after the MMIO read, rather than before it?
> > Typically the barrier should ensure that any read from memory after an
> > MMIO read reflects the memory contents after any DMA is complete that
> > the MMIO
Hi Arnd
On Mon, 18 Feb 2013, Arnd Bergmann wrote:
> On Friday 15 February 2013, Guennadi Liakhovetski wrote:
> > Without barriers SDIO operations fail with runtime PM enabled.
>
> I don't understand how the changeset comment relates to the patch.
>
> > diff --git a/drivers/mmc/host/tmio_mmc.h b
On Fri, Feb 15, 2013 at 01:36:30PM +0100, Peter De Schrijver wrote:
> This is the seventh version of the Tegra114 clockframework. It is based on the
> for-next branch of
> git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra.git and
> http://www.spinics.net/lists/arm-kernel/msg220452.h
On 2/18/2013 7:06 PM, Peter Korsgaard wrote:
"M" == Mugunthan V N writes:
M> The CPSW switch can act as Dual EMAC by segregating the switch ports
M> using VLAN and port VLAN as per the TRM description in
M> 14.3.2.10.2 Dual Mac Mode
M> Following CPSW components will be common for both
On Friday 15 February 2013, Guennadi Liakhovetski wrote:
> Without barriers SDIO operations fail with runtime PM enabled.
I don't understand how the changeset comment relates to the patch.
> diff --git a/drivers/mmc/host/tmio_mmc.h b/drivers/mmc/host/tmio_mmc.h
> index d857f5c..a10ebd0 100644
> -
On Friday 15 February 2013, Guennadi Liakhovetski wrote:
> This is v4 of a patch-series, extending mmc subsystem device-tree usage
> and adding more advanced DT capabilities to sh_mmcif and sh_mobile_sdhi /
> tmio_mmc drivers. Changes since v3 are described in respective patches.
> Thanks to all
On Sun, Feb 10, 2013 at 11:35 AM, Javier Martinez Canillas
wrote:
> On Sun, Feb 10, 2013 at 10:37 AM, Russell King - ARM Linux
> wrote:
>> On Sun, Feb 10, 2013 at 02:49:21AM +0100, Javier Martinez Canillas wrote:
>>> I knew this would be controversial and that's why I didn't mean it to be a
>>>
>
> On Fri, Feb 15, 2013 at 11:06:10AM -0500, Justin Sobota wrote:
> > This commit adds a license header to fdt.h and libfdt_env.h because the l=
> icense was omitted.
> >=20
> > Signed-off-by: Justin Sobota
> Acked-by: David Gibson
Applied!
Thanks,
jdl
Hi Steffen,
On 2013-01-25 11:01, Steffen Trumtrar wrote:
> +/* VESA display monitor timing parameters */
> +#define VESA_DMT_HSYNC_LOW BIT(0)
> +#define VESA_DMT_HSYNC_HIGH BIT(1)
> +#define VESA_DMT_VSYNC_LOW BIT(2)
> +#define VESA_DMT_VSYNC_HIGH BIT(3)
> +
On 02/18/2013 02:51 PM, Grant Likely wrote:
> On Sun, Feb 10, 2013 at 11:35 AM, Javier Martinez Canillas
> wrote:
>> On Sun, Feb 10, 2013 at 10:37 AM, Russell King - ARM Linux
>> wrote:
>>> On Sun, Feb 10, 2013 at 02:49:21AM +0100, Javier Martinez Canillas wrote:
I knew this would be controv
On 02/18/2013 12:30 AM, Afzal Mohammed wrote:
> Register percpu local timer for scheduler tick in the case of one core
> SMP configuration. In other cases - secondary cpu's as well as boot
> cpu's having more than one core, this is being registered as per
> existing boot flow, with a difference tha
> "M" == Mugunthan V N writes:
M> The CPSW switch can act as Dual EMAC by segregating the switch ports
M> using VLAN and port VLAN as per the TRM description in
M> 14.3.2.10.2 Dual Mac Mode
M> Following CPSW components will be common for both the interfaces.
M> * Interrupt source is com
On Sun, Feb 10, 2013 at 9:37 AM, Russell King - ARM Linux
wrote:
> On Sun, Feb 10, 2013 at 02:49:21AM +0100, Javier Martinez Canillas wrote:
>> I knew this would be controversial and that's why I didn't mean it to be a
>> patch
>> but a RFC :)
>>
>> The problem basically is that you have to assoc
On 15.2.2013 17:25, Stephen Warren wrote:
> On 02/15/2013 01:52 AM, Hiroshi Doyu wrote:
>> This patch allows kernel source to include those DT
>> headers. For example:
>>
>> + #include
>>
>> Signed-off-by: Hiroshi Doyu
>> ---
>> Makefile |2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-
Hi Guennadi,
On Fri, Feb 15 2013, Guennadi Liakhovetski wrote:
> This is v4 of a patch-series, extending mmc subsystem device-tree usage
> and adding more advanced DT capabilities to sh_mmcif and sh_mobile_sdhi /
> tmio_mmc drivers. Changes since v3 are described in respective patches.
> Thanks
Hi,
On Mon, Feb 18, 2013 at 11:26:38AM +0100, Daniel Mack wrote:
> On 10.01.2013 21:22, Tony Lindgren wrote:
> > * Andreas Fenkart [121220 14:15]:
> >> Without functional clock the omap_hsmmc module can't forward
> >> SDIO IRQs to the system. This patch reconfigures dat1 line
> >> as a gpio while
Hi Javier,
On 2/16/2013 5:44 PM, Javier Martinez Canillas wrote:
On Sat, Feb 16, 2013 at 2:09 PM, Anil Kumar wrote:
Hi Florian,
On Mon, Jan 28, 2013 at 11:24 PM, Florian Vaussard
wrote:
Add device-tree support for the GPMC controller on the OMAP3.
Signed-off-by: Florian Vaussard
---
arc
AM43 SoC is in pre-silicon stage, meanwhile it has been modelled in
a pre-silicon platform. To validate and boot Linux in pre-silicon
platform that emulates an AM43 SoC, add DT build support.
As bootloader is not used, bootargs is passed through DT.
Note: This would be replaced by an original boa
DT source (minimal) for AM4372 SoC. Those represented here are the
minimal DT nodes necessary to get kernel booting.
Signed-off-by: Afzal Mohammed
---
arch/arm/boot/dts/am4372.dtsi | 55 +++
1 file changed, 55 insertions(+)
create mode 100644 arch/arm/boo
Describe minimal DT boot machine details for AM43 based SoC's. AM43
family of SoC's are ARM Cortex-A9 based with one core in SMP
configuration. Low level debug could be achieved by selecting
DEBUG_AM33XXUART1. To boot AM43 SoC, this change is sufficient w.r.t
Kernel (considering the fact that stric
Add Kconfig option for AM43 family of SoC's, these are ARM Cortex A9
based (SMP configuration with 1 core).
Signed-off-by: Afzal Mohammed
---
arch/arm/mach-omap2/Kconfig | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
ind
Selecting DEBUG_AM33XXUART1 routes low level debug messages to first
UART instance of AM335x based SoC's. This selection is valid for
upcoming AM43 based SoC's too. Make this information available upon
configuring.
Signed-off-by: Afzal Mohammed
---
arch/arm/Kconfig.debug | 3 +++
1 file changed,
Add an optional property to find clock-frequency from DT. This helps
as a fallback mechanism in case there is no representation of clock
tree in DT.
Signed-off-by: Afzal Mohammed
---
Documentation/devicetree/bindings/arm/twd.txt | 7 ++-
arch/arm/kernel/smp_twd.c | 8
Register percpu local timer for scheduler tick in the case of one core
SMP configuration. In other cases - secondary cpu's as well as boot
cpu's having more than one core, this is being registered as per
existing boot flow, with a difference that they happens after delay
calibration. Registering th
Return percpu clock event on local timer register. It is the boot cpu
that calls this and it can use the returned percpu clock event to
register a clock event in the case of SMP configuration with one core.
This helps to have a booting Kernel even if no other timer is
registered for clock tick.
Si
(Resending, since it seems, LAKML doesn't accept patches with subject
prefix only as "RFC", but requires "PATCH" prefix also)
Hi,
This series adds minimal support to boot Linux on platforms having
AM43 based SoC's.
This is being sent as an RFC to seek opinion about modification in
twd to registe
On 02/16/2013 08:33 AM, Anil Kumar wrote:
> Add the needed sections to enable audio support on
> Devkit8000 when booted with DT blob.
>
> Signed-off-by: Anil Kumar
Looks good:
Acked-by: Peter Ujfalusi
> ---
> This patch is based on top of kernel 3.8-rc5 and
> the following patches.
>
> Peter
On 10.01.2013 21:22, Tony Lindgren wrote:
> * Andreas Fenkart [121220 14:15]:
>> 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. And uses SDIO IRQ detection of
>> the module, while fclk i
Hi Sebastian,
On 09.02.2013 13:59, Sebastian Hesselbarth wrote:
> This patch adds a common clock driver for Silicon Labs Si5351a/b/c
> i2c programmable clock generators. Currently, the driver supports
> DT kernels only and VXCO feature of si5351b is not implemented. DT
> bindings selectively allow
Add device-tree bindings to the AS3711 regulator and backlight drivers.
Signed-off-by: Guennadi Liakhovetski
---
v2:
1. remove of_device_is_available() - it breaks compilation with CONFIG_OF
disabled and is redundant anyway - I2C devices are only registered for
available devoces
2. add parenth
Hi,
[...]
> +static void samsung_timer_parse_dt(struct device_node *np,
> + const struct of_device_id *match)
> +{
> + int i;
> + u32 val;
> +
> + timer_base = of_iomap(np, 0);
> + if (!timer_base)
> + panic("failed to map timer regi
On Fri, Feb 15, 2013 at 01:16:17PM +, Linus Walleij wrote:
> n Thu, Feb 14, 2013 at 8:17 PM, Thierry Reding
> wrote:
> > On Thu, Feb 14, 2013 at 04:53:41PM +, Andrew Murray wrote:
> >> Thierry,
> >>
> >> If you don't have much bandwidth I'd be quite happy to take this on - this
> >> would
On Sun, 17 Feb 2013, Simon Horman wrote:
> On Sun, Feb 17, 2013 at 04:52:16PM +0900, Simon Horman wrote:
> > On Sat, Feb 16, 2013 at 05:58:25PM +0100, Sascha Hauer wrote:
> > > Hi Guennadi,
> > >
> > > On Sat, Feb 16, 2013 at 04:21:16PM +0100, Guennadi Liakhovetski wrote:
> > > > MMC defines a nu
Hi Sergei
On Sun, 17 Feb 2013, Sergei Shtylyov wrote:
> Hello.
>
> On 02/15/2013 06:14 PM, Guennadi Liakhovetski wrote:
>
> > Many MMC capability flags are platform-dependent and are traditionally set
> > in platform data. With DT often each such capability requires a special
> > binding. Add b
On Mon, Feb 18, 2013 at 5:21 PM, Thomas Abraham
wrote:
> Since the clock initialization should be completed prior to the mct timer
> initialization, create a new function 'exynos_init_time' that first sets up
> the clock and then invokes the timer initialization function. The 'init_time'
> callbac
The clock frequency of xxti and xusbxti clocks is dependent on the frequency of
the
on-board oscillator that is used to generate these clocks. So allow the
frequency
of these clocks to be specfied from device tree.
Cc: Kukjin Kim
Signed-off-by: Thomas Abraham
---
arch/arm/boot/dts/exynos4210-
For all supported peripheral controllers on Exynos5440, add clock lookup
information.
Cc: Kukjin Kim
Signed-off-by: Thomas Abraham
---
arch/arm/boot/dts/exynos5440.dtsi | 18 ++
1 files changed, 18 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/exynos5440.dtsi
For all supported peripheral controllers on Exynos5250, add clock lookup
information.
Cc: Kukjin Kim
Signed-off-by: Thomas Abraham
---
arch/arm/boot/dts/exynos5250.dtsi | 72 +
1 files changed, 72 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dt
For all supported peripheral controllers on Exynos4 SoCs, add clock lookup
information.
Cc: Kukjin Kim
Reviewed-by: Sylwester Nawrocki
Tested-by: Sylwester Nawrocki
Reviewed-by: Tomasz Figa
Tested-by: Tomasz Figa
Signed-off-by: Thomas Abraham
---
arch/arm/boot/dts/exynos4.dtsi| 50 +++
Add clock controller nodes for Exynos4210, Exynos4x12, Exynos5250 and
Exynos5440 SoC.
Cc: Kukjin Kim
Signed-off-by: Thomas Abraham
---
arch/arm/boot/dts/exynos4210.dtsi |6 ++
arch/arm/boot/dts/exynos4x12.dtsi |6 ++
arch/arm/boot/dts/exynos5250.dtsi |6 ++
arch/arm/boot
Add support for mct clock lookup and setup to ensure that the mct clock
is has been turned on.
Cc: Kukjin Kim
Signed-off-by: Thomas Abraham
---
drivers/clocksource/exynos_mct.c |7 ++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/drivers/clocksource/exynos_mct.c b/driv
With the migration of Exynos4 clocks to use common clock framework, the old
styled 'xtal' clock is not used anymore. Instead, the clock 'fin_pll' is used
as the tick clock for mct controller.
Cc: Kukjin Kim
Signed-off-by: Thomas Abraham
---
drivers/clocksource/exynos_mct.c |9 ++---
1 f
With support for device tree based clock lookup now available, remove the
auxdata table from exynos4/5 dt-enabled machine file.
Cc: Kukjin Kim
Signed-off-by: Thomas Abraham
---
arch/arm/mach-exynos/mach-exynos4-dt.c | 69 +--
arch/arm/mach-exynos/mach-exynos5-dt.c | 98 +
The clock speed of xxti and xusbxti clocks depends on the oscillator used on the
board to generate these clocks. For non-dt platforms, allow the board support
for those platforms to set the clock frequency of xxti and xusbxti clocks.
Cc: Kukjin Kim
Signed-off-by: Thomas Abraham
---
arch/arm/mac
Since the clock initialization should be completed prior to the mct timer
initialization, create a new function 'exynos_init_time' that first sets up
the clock and then invokes the timer initialization function. The 'init_time'
callback in the board files are updated to invoke this new wrapper func
The Exynos5440 clocks are statically listed and registered using the Samsung
specific common clock helper functions.
Cc: Mike Turquette
Cc: Kukjin Kim
Signed-off-by: Thomas Abraham
---
.../devicetree/bindings/clock/exynos5440-clock.txt | 61 +
drivers/clk/samsung/Makefile
The Exynos5250 clocks are statically listed and registered using the Samsung
specific common clock helper functions. Both device tree based clock lookup
and clkdev based clock lookups are supported.
Cc: Mike Turquette
Cc: Kukjin Kim
Signed-off-by: Thomas Abraham
---
.../devicetree/bindings/clo
The Exynos4 clocks are statically listed and registered using the Samsung
specific common clock helper functions. Both device tree based clock lookup
and clkdev based clock lookups are supported.
Cc: Mike Turquette
Cc: Kukjin Kim
Reviewed-by: Sylwester Nawrocki
Tested-by: Sylwester Nawrocki
Re
There are several types of pll clocks used in Samsung SoC's and these pll
clocks can be represented as Samsung specific pll clock types and registered
with the common clock framework. Add support for pll35xx, pll36xx, pll45xx,
pll46xx and pll2550x clock types and helper functions to register them.
All Samsung platforms include different types of clock including fixed-rate,
mux, divider and gate clock types. There are typically hundreds of such clocks
on each of the Samsung platforms. To enable Samsung platforms to register these
clocks using the common clock framework, a bunch of utility fun
Changes since v5:
- Squashed several Exynos4 fixes patch from Tomasz Figa
- Included support for Exynos5250 and Exynos5440, thus converting all
Exynos4 and Exynos5 platforms to common clock framework.
- Depends on the following patch series.
- http://www.mail-archive.com/linux-samsung-soc@vger.
Move the multi core timer (mct) driver to from mach-exynos to
drivers/clocksource and update the Kconfig and makefiles.
Cc: Changhwan Youn
Signed-off-by: Thomas Abraham
Reviewed-by: Stephen Warren
---
arch/arm/Kconfig |2 +-
arch/arm/mach-exynos/Kconfig
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
Reviewed-by: Stephen Warren
---
arch/arm/mach-exynos/c
Add MCT device tree node for Exynos4210, Exynos4212, Exynos4412 and Exynos5250.
Cc: Changhwan Youn
Signed-off-by: Thomas Abraham
Reviewed-by: Stephen Warren
---
arch/arm/boot/dts/exynos4210.dtsi | 22 ++
arch/arm/boot/dts/exynos4212.dtsi | 22 ++
arc
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
Reviewed-by: Stephen Warr
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 v4:
- Rebased to 3.8-rc7
- Updated the MCT controller device nodes to list all the four global timer
interrupts generated by the MCT controller.
Changes since v3:
- Based on Stephen Warren's CONFIG_CLKSRC_OF patches (merged from arm-soc
'timer/cleanup' branch).
- Moved the mct dr
81 matches
Mail list logo
