On 3/20/2013 11:51 AM, Santosh Shilimkar wrote:
> Russell,
>
> In last couple of months, I have observed that users are getting knocked off
> from LAKML often. I myself faced it 2 times so far and I heard similar
> complaint
> at least from 5 more folks.
>
> Is there a change in settings or some
Add phy_id device tree data to am335x-evmsk device to bring up CPSW
ethernet present on am335x starter kit.
Signed-off-by: Mugunthan V N
---
arch/arm/boot/dts/am335x-evmsk.dts |8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/am335x-evmsk.dts
b/arch/arm/boot/dts/a
Yes ill fix it up and move the doc to the other patch and send a v2
From: Shilimkar, Santosh
Sent: Wednesday, March 20, 2013 1:22 AM
To: Taneja, Archit
Cc: Gross, Andy; linux-omap@vger.kernel.org; Cousson, Benoit;
devicetree-disc...@lists.ozlabs.org; Meno
On Wednesday 20 March 2013 11:46 AM, Archit Taneja wrote:
> On Wednesday 20 March 2013 11:26 AM, Santosh Shilimkar wrote:
>> On Wednesday 20 March 2013 10:13 AM, Andy Gross wrote:
>>> Remove DMM device creation via the hwmod entry. The DMM device will
>>> now be enumerated as part of the device tr
Russell,
In last couple of months, I have observed that users are getting knocked off
from LAKML often. I myself faced it 2 times so far and I heard similar complaint
at least from 5 more folks.
Is there a change in settings or something new which started triggering this ?
Regards,
Santosh
--
T
On Wednesday 20 March 2013 11:26 AM, Santosh Shilimkar wrote:
On Wednesday 20 March 2013 10:13 AM, Andy Gross wrote:
Remove DMM device creation via the hwmod entry. The DMM device will
now be enumerated as part of the device tree information for the
processor.
Signed-off-by: Andy Gross
---
O
On Tuesday 19 March 2013 11:23 PM, Nishanth Menon wrote:
> We now use Soc generic cpufreq-cpu0 driver using DT entries.
> However to allow cpufreq-cpu0 and omap-cpufreq drivers to co-exist,
> we need to ensure the following using the same image:
> 1. With device tree boot, we use cpufreq-cpu0
> 2.
On Wednesday 20 March 2013 10:13 AM, Andy Gross wrote:
> Add DMM bindings for OMAP4 and OMAP5 devices.
>
> Signed-off-by: Andy Gross
> ---
> arch/arm/boot/dts/omap4.dtsi |7 +++
> arch/arm/boot/dts/omap5.dtsi |7 +++
> 2 files changed, 14 insertions(+), 0 deletions(-)
>
"Documen
On Wednesday 20 March 2013 10:13 AM, Andy Gross wrote:
> Remove DMM device creation via the hwmod entry. The DMM device will
> now be enumerated as part of the device tree information for the
> processor.
>
> Signed-off-by: Andy Gross
> ---
OMAP4 is still not made DT only so I suggest you to hol
Remove DMM device creation via the hwmod entry. The DMM device will
now be enumerated as part of the device tree information for the
processor.
Signed-off-by: Andy Gross
---
Documentation/devicetree/bindings/arm/omap/dmm.txt | 16
arch/arm/mach-omap2/drm.c
This patch set adds devicetree bindings for the Dynamic Memory Manager (DMM)
inside the OMAP4 and OMAP5 devices, removes generation of the device node via
the hwmod, and adds documentation for the minimal binding.
This patch series is based on device tree patches queued up for OMAP 3.10.
Patches
Add DMM bindings for OMAP4 and OMAP5 devices.
Signed-off-by: Andy Gross
---
arch/arm/boot/dts/omap4.dtsi |7 +++
arch/arm/boot/dts/omap5.dtsi |7 +++
2 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index
On 10:54-20130319, Eduardo Valentin wrote:
> This patch updates the documentation to remove
> all warnings and errors reported by scripts/kernel-doc.
> Most are missing arguments due to wrong format.
>
> Cc: Nishanth Menon
>
> Signed-off-by: Eduardo Valentin
> ---
&
Hi Felipe,
* Roger Quadros [130315 08:20]:
> Hi Tony,
>
> These patches provide the SoC side code required to support
> the changes in the OMAP USB Host drivers done in [1], [2] & [3].
>
> Device tree support is added for Beagleboard and Panda.
>
> NOTE: The first patch needs to be shared betw
Hi,
* Mark Jackson [130312 13:48]:
> I'm struggling to get the latest kernel git to load on my beaglebone.
>
> Error: unrecognized/unsupported machine ID (r1 = 0x0e05).
>
> I guess I'm missing some vital step ?
We're changing the mainline kernel tree to use device tree
based booting only.
* Peter Ujfalusi [130318 03:16]:
> Hi Tony,
>
> I have rebased the branch on 3.9-rc3 tag.
> Is it still possible to send this for 3.9?
Let's see if we can still get this in. It's getting a bit late
for v3.9, so I'll apply this into a separate branch from other fixes
omap-for-v3.9-rc3/fix-twl-reb
* Paul Walmsley [130314 11:56]:
> Hi Tony,
>
> The following changes since commit f6161aa153581da4a3867a2d1a7caf4be19b6ec9:
>
> Linux 3.9-rc2 (2013-03-10 16:54:19 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git
> ta
On Tue, 19 Mar 2013 13:51:01 +0200, Pantelis Antoniou
wrote:
> Hi Grant,
>
> On Mar 16, 2013, at 11:24 AM, Grant Likely wrote:
>
> > On Wed, 23 Jan 2013 12:58:02 +0200, Pantelis Antoniou
> > wrote:
> >> Hi David,
> >>
> >> On Jan 23, 2013, at 6:40 AM, David Gibson wrote:
> >>> Ok. Nonethele
On Tue, 19 Mar 2013 13:42:32 +0200, Pantelis Antoniou
wrote:
> Hi Grant,
>
> The 3rd patch is in preparation for some patches I have in WIP that would
> allow
> drivers to set notifications for properties that are changed in runtime.
Okay, submit it with that series then please.
g.
--
To uns
* Rajendra Nayak [130319 03:43]:
> clk inits on OMAP happen quite early, even before slab is available.
> The dependency comes from the fact that the timer init code starts to
> use clocks and hwmod and we need clocks to be initialized by then.
>
> There are various problems doing clk inits this
Hi Russell,
Can we use your commit 71856843 (ARM: OMAP: use consistent error checking)
as an immutable base for further omap dmtimer and gpmc work?
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More ma
PandaBoard, PandaBoard-A4 revisions use OMAP4430.
PandaBoard-ES version of the board uses OMAP4460.
Move the original panda dts file into a common dtsi used by all panda
variants. This allows us to introduce SoC variation for PandaBoard ES
without impacting other PandaBoard versions that are suppo
Hi,
The following version 2 of the series arose from trying to use BeagleBoard-XM
(OMAP3 variant) for doing CPU DVFS using cpufreq-cpu0. This series enables the
generic cpufreq-cpu0 driver to be used in device tree enabled boot while
maintaining support of the legacy omap-cpufreq driver when used i
Define VDD1 regulator in twl4030 DT and mark it as the supply for the
various OMAP34xx/35xx/36xx/37xx platforms (all use TWL4030 variants with
VDD1 supplying the CPU).
NOTE: This currently will use I2C1 bus communication path to set the
voltage in device tree boot. In the legacy non device tree bo
Add DT OPP table for OMAP34xx/35xx family of devices. This data is
decoded by OF with of_init_opp_table() helper function.
OPP data here is based on existing opp3xxx_data.c
Since the omap36xx OPP tables would be different from OMAP34xx/35xx,
introduce an new omap34xx.dtsi for 34xx/35xx specific e
Add DT OPP table for OMAP443x family of devices. This data is
decoded by OF with of_init_opp_table() helper function.
OPP data here is based on existing opp4xxx_data.c
Since the omap4460 OPP tables would be different from OMAP443x,
introduce an new omap443x.dtsi for 443x specific entries and use
Add DT OPP table for OMAP36xx/37xx family of devices. This data is
decoded by OF with of_init_opp_table() helper function.
OPP data here is based on existing opp3xxx_data.c
This is in preparation to use generic cpufreq-cpu0 driver for device
tree enabled boot. Legacy non device tree enabled boot
We now use Soc generic cpufreq-cpu0 driver using DT entries.
However to allow cpufreq-cpu0 and omap-cpufreq drivers to co-exist,
we need to ensure the following using the same image:
1. With device tree boot, we use cpufreq-cpu0
2. With non device tree boot, we use omap-cpufreq
In the case of (1),
With OMAP3+ and AM33xx supported SoC having defined CPU device tree
entries with operating-points defined, we can now use the SoC
generic cpufreq-cpu0 driver by registering appropriate device.
As part of this change, add dummy clock node to use cpufreq-cpu0.
This is an suggested solution till we h
Add DT OPP table for OMAP4460 family of devices. This data is
decoded by OF with of_init_opp_table() helper function.
OPP data here is based on existing opp4xxx_data.c
This is in preparation to use generic cpufreq-cpu0 driver for device
tree enabled boot. Legacy non device tree enabled boot conti
From: NeilBrown
The context loss handling in dmtimer appears to assume that
omap_dm_timer_set_load_start() or omap_dm_timer_start() and
omap_dm_timer_stop() bracket all interactions. Only the first two
restore the context and the last updates the context loss counter.
However omap_dm_timer_set_l
Update the DMTIMER compatibility property to reflect the register level
compatibilty between devices and update the various OMAP/AM timer
bindings with the appropriate compatibility string.
By doing this we can add platform specific data applicable to specific
timer versions to the driver. For exa
Add a function so that OMAP dmtimers can be requested by device-tree
node. This allows for devices, such as the internal DSP, or drivers,
such as PWM, to reference a specific dmtimer node via the device-tree.
Given that there are several APIs available for requesting dmtimers
(by ID, by capability
Currently the DMTIMER errata flags are not being populated when using
device-tree. Add static platform data to populate errata flags when
using device-tree.
Please note that DMTIMER erratum i767 is applicable to OMAP3-5 devices
as well as AM335x devices.
Signed-off-by: Jon Hunter
---
arch/arm/p
When booting with device-tree the function pointer for detecting context
loss is not populated. Ideally, the pm_runtime framework should be
enhanced to allow a means for reporting context/state loss and we could
avoid populating such function pointers altogether. In the interim until
a generic non-
Includes:
- A couple fixes for DMTIMER context loss handling.
- Populating DMTIMER errata when booting with device-tree.
- A new function for requesting a DMTIMER by device-tree node.
Based upon v3.9-rc3.
Tested on OMAP5912 OSK, OMAP2420 H4, OMAP3430 SDP, OMAP4430 Blaze
and AM335x EVM. Testing in
Use PTR_RET function instead of IS_ERR and PTR_ERR.
Patch found using coccinelle.
Signed-off-by: Alexandru Gheorghiu
---
drivers/video/omap2/dss/core.c |5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/video/omap2/dss/core.c b/drivers/video/omap2/dss/core.c
index
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tony
The following changes since commit a937536b868b8369b98967929045f1df54234323:
Linux 3.9-rc3 (2013-03-17 15:59:32 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git
tags/omap
Some of the GPMC timings parameters are currently missing from the GPMC
device-tree binding. Add these parameters to the binding documentation
as well as code to read them. Also add either "-ps" or "-ns" suffix to
the GPMC timing properties to indicate whether the timing is in
picoseconds or nanose
With commit 21cc2bd (ARM: OMAP2+: Remove apollon board support) the
variable "boot_rom_space" is now not needed and the code surrounding
this variable can be cleaned up and simplified. Remove unnecessary
definitions and clean-up the comment as well.
Signed-off-by: Jon Hunter
Tested-by: Ezequiel G
From: Javier Martinez Canillas
gpmc_probe_nor_child() calls of_platform_device_create() to create a
platform device for the NOR child. If this function fails the value
of ret is returned to the caller but this value is zero since it was
assigned the return of a previous call to gpmc_cs_program_se
NOR flash is not currently supported when booting with device-tree
on OMAP2+ devices. Add support to detect and configure NOR devices
when booting with device-tree.
Add documentation for the TI GPMC NOR binding.
Signed-off-by: Jon Hunter
Tested-by: Ezequiel Garcia
---
Documentation/devicetree/
Each GPMC chip-select can be configured to map 16MB, 32MB, 64MB or 128MB
of address space. The physical base address where a chip-select starts
is also configurable and must be aligned on a boundary that is equal to
or greater than the size of the address space mapped bt the chip-select.
When enabl
When the GPMC driver is probed, we call gpmc_mem_init() to see which
chip-selects have already been configured and enabled by the boot-loader
and allocate space for them. If we fail to allocate space for one
chip-select, then we return failure from the probe and the GPMC driver
will not be availabl
When booting with device-tree, retrieve GPMC settings for ONENAND from
the device-tree blob. This will allow us to remove all static settings
stored in the gpmc-nand.c in the future once the migration to
device-tree is complete.
The user must now specify the ONENAND device width in the device-tree
Convert the OMAP2+ SMC91x code to use the gpmc_cs_program_settings()
function for configuring the various GPMC options instead of directly
programming the CONFIG1 register.
Move configuration of the GPMC settings outside retime function and
this does not need to be done if the timings are changed
When booting with device-tree, retrieve GPMC settings for NAND from
the device-tree blob. This will allow us to remove all static settings
stored in the gpmc-nand.c in the future once the migration to
device-tree is complete.
Signed-off-by: Jon Hunter
Tested-by: Ezequiel Garcia
---
arch/arm/mac
Adds a function to read the various GPMC chip-select settings from
device-tree and store them in the gpmc_settings structure.
Update the GPMC device-tree binding documentation to describe these
options.
Signed-off-by: Jon Hunter
Tested-by: Ezequiel Garcia
---
Documentation/devicetree/bindings/
With the addition of the gpmc_cs_program_settings(), we no longer need
or use gpmc_cs_configure() to configure some of the GPMC chip-select
options. So rename the function to gpmc_configure() and remove code that
modifies options in the CONFIG1 register.
Signed-off-by: Jon Hunter
Tested-by: Ezequ
Convert the OMAP2+ TUSB code to use the gpmc_cs_program_settings()
function for configuring the various GPMC options instead of directly
programming the CONFIG1 register.
Signed-off-by: Jon Hunter
Tested-by: Ezequiel Garcia
---
arch/arm/mach-omap2/usb-tusb6010.c | 43 -
Convert the OMAP2+ NAND code to use the gpmc_cs_program_settings()
function for configuring the various GPMC options instead of directly
programming the CONFIG1 register.
This moves the configuration of some GPMC options outside the
nand_gpmc_retime() because these options should only need to be s
Convert the OMAP2+ ONENAND code to use the gpmc_cs_program_settings()
function for configuring the various GPMC options instead of directly
programming the CONFIG1 register.
Signed-off-by: Jon Hunter
Tested-by: Ezequiel Garcia
---
arch/arm/mach-omap2/gpmc-onenand.c | 61 +++---
The GPMC has various different configuration options such as bus-width,
synchronous or asychronous mode selection, burst mode options etc.
Currently, there is no common function for configuring these options and
various devices set these options by either programming the GPMC CONFIG1
register direc
The GPMC has various different configuration options such as bus-width,
synchronous or asychronous mode selection, burst mode options etc.
Currently, there is no central structure for storing all these options
when configuring the GPMC for a given device. Some of the options are
stored in the GPMC
The GPMC has wait-pin signals that can be assigned to a chip-select
to monitor the ready signal of an external device. Add a variable to
indicate the total number of wait-pins for a given device. This will
allow us to detect if the wait-pin being selected is valid or not.
When booting with device-
While adding device-tree support for NOR memories, it became apparent
that there is no common way for configuring various GPMC settings for
devices that interface to the GPMC. These settings include bus-width,
synchronous/asynchronous mode, burst settings, wait monitoring etc.
Therefore, to simplif
The OMAP2+ code that configures the GPMC for ONENAND devices is copying
structures between functions unnecessarily. Avoid this by passing
pointers instead and simplify the code.
A pointer to structure "omap_onenand_platform_data" is passed to the
function omap2_onenand_calc_sync_timings(), but onl
On 16:17-20130319, Guillaume Gardet wrote:
> Hi,
>
> On a Beagleboard xM rev. B, I noticed that vanilla kernel 3.4.6 have the
> folowing bogomips for 300MHz and 800 MHz operations: 262.08 and 700.57.
>
> With kernel 3.7.10, I have : 175.65 and 467.41 bogompis.
>
> Any
Vinod, Tony, Benoit,
On 02/26/2013 12:27 PM, Jon Hunter wrote:
> If the device-tree blob is present during boot, then register the SDMA
> controller with the device-tree DMA driver so that we can use device-tree
> to look-up DMA client information.
>
> Signed-off-by: Jon Hunter
> Reviewed-by: Fe
Hi,
On a Beagleboard xM rev. B, I noticed that vanilla kernel 3.4.6 have the
folowing bogomips for 300MHz and 800 MHz operations: 262.08 and 700.57.
With kernel 3.7.10, I have : 175.65 and 467.41 bogompis.
Any idea why bogomips are so low now?
Guillaume
--
To unsubscribe from this list: send
Move _ti_bandgap_write_threshold and _ti_bandgap_read_threshold to static
area, as they are local functions.
Signed-off-by: Eduardo Valentin
---
drivers/staging/ti-soc-thermal/ti-bandgap.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/ti-soc-ther
While writing talert thresholds, propagate the error code from
ti_bandgap_update_alert_threshold to the caller of
_ti_bandgap_write_threshold.
Signed-off-by: Eduardo Valentin
---
drivers/staging/ti-soc-thermal/ti-bandgap.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a
Wrong threshold cold values may be written with current implementation.
This patch fixes the threshold update function by simplifying the
bitfield manipulation sequence.
Signed-off-by: Eduardo Valentin
---
drivers/staging/ti-soc-thermal/ti-bandgap.c |8
1 files changed, 4 insertions
While updating talert thresholds, threshold cold must
always be lower than threshold hot. This patch fixes
the function ti_bandgap_update_alert_threshold to only
change the thresholds by applying a hysteresis when
they violate this condition.
Signed-off-by: Eduardo Valentin
---
drivers/staging/t
This patch updates the documentation to remove
all warnings and errors reported by scripts/kernel-doc.
Most are missing arguments due to wrong format.
Cc: Nishanth Menon
Signed-off-by: Eduardo Valentin
---
drivers/staging/ti-soc-thermal/ti-bandgap.c | 56 +-
drivers/s
This patch changes the data structures of this driver so
that readonly data can reside only in the conf pointer.
Now each register has a struct to hold its configuration info,
to be used base on chip version for instance, and a
struct of values to be written, like register shadow and priv data.
Si
Follow Documentation/CodingStyle and use sizeof(*pointer)
instead of sizeof(struct type).
Signed-off-by: Eduardo Valentin
---
drivers/staging/ti-soc-thermal/ti-bandgap.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/ti-soc-thermal/ti-bandgap.c
b/driv
This patch renames the Kconfig options to cope with
the new naming convention.
Cc: Santosh Shilimkar
Cc: Benoit
Cc: Nishanth Menon
Cc: Dan Carpenter
Signed-off-by: Eduardo Valentin
---
drivers/staging/Makefile|2 +-
drivers/staging/ti-soc-thermal/Kconfig | 14
Because this driver will support also OMAP derivatives,
this patch does a big rename inside this driver, so it
better fits its usage.
This patch only renames the directory, file names,
includes, Makefiles and Kconfig includes.
Cc: Santosh Shilimkar
Cc: Benoit
Cc: Nishanth Menon
Cc: Dan Carpent
Use a shorter name to bandgap pointer.
Cc: Benoit
Cc: Dan Carpenter
Signed-off-by: Eduardo Valentin
---
drivers/staging/omap-thermal/omap-bandgap.c| 562 ++--
drivers/staging/omap-thermal/omap-bandgap.h| 28 +-
drivers/staging/omap-thermal/omap-thermal-commo
Return the proper error value in _omap_bandgap_read_threshold.
Acked-by: Dan Carpenter
Signed-off-by: Eduardo Valentin
---
drivers/staging/omap-thermal/omap-bandgap.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/staging/omap-thermal/omap-bandgap.c
b/drivers
Hello Greg,
This is version 2 of this series to rename omap-thermal driver
inside staging tree. V1 is found here:
http://lkml.org/lkml/2013/3/18/357
The idea of the series is the same. It includes several fixes, but
the major change is that now the driver will be named ti-soc-thermal,
because it
Hello Greg,
On 18-03-2013 10:59, Eduardo Valentin wrote:
Hi Greg,
I am sending extra patches on omap-thermal driver, under staging.
There are couple of fixes based on Dan Carpenter's review on
the last patch set I sent. On top of these, there are some
changes on the naming convention for this
On 03/19/2013 04:26 PM, Roger Quadros wrote:
> Register a device tree clock provider for AUX clocks
> on the OMAP4 SoC. Also provide the binding information.
>
> Signed-off-by: Roger Quadros
> ---
> .../devicetree/bindings/clock/omap4-clock.txt | 32 ++
> arch/arm/boot/dts
Hi,
Based on the discussion in [1], I've implemented device tree
provider for the AUXCLKs on OMAP4.
Please let me know if there are any issues.
This is important to get USB Host support working on Panda with
device tree boot on 3.10.
Roger Quadros (2):
ARM: OMAP4: clock: Add device tree suppo
Register a device tree clock provider for AUX clocks
on the OMAP4 SoC. Also provide the binding information.
Signed-off-by: Roger Quadros
---
.../devicetree/bindings/clock/omap4-clock.txt | 32 ++
arch/arm/boot/dts/omap4.dtsi |5 +++
arch/arm/mach
The USB PHY needs AUXCLK3 to operate. Provide this information
in the device tree.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap4-panda.dts |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap4-panda.dts
b/arch/arm/boot/dts/omap4-panda.dts
i
On 03/19/2013 04:26 PM, Roger Quadros wrote:
> Hi,
>
> Based on the discussion in [1], I've implemented device tree
> provider for the AUXCLKs on OMAP4.
[1] - https://lkml.org/lkml/2013/3/12/241
cheers,
-roger
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body o
Add l3-noc node for OMAP4 and OMAP5 devices.
Cc: Benoit Cousson
Signed-off-by: Santosh Shilimkar
---
arch/arm/boot/dts/omap4.dtsi |5 +
arch/arm/boot/dts/omap5.dtsi |5 +
2 files changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
OMAP hwmod layer does the reset of the IPs in early code so that
we have SOC in sane state. To do the soft-reset, it needs to ioremap()
the ip address space to be able to write to sysconfig registers.
But there are few hwmod which doesn't have sysconfig registers and hence
no need to ioremap() the
Patch adds the code for extracting the module ocp address space from device
tree blob in case the hwmod address space look up fails.
The idea is to remove the address space data from hwmod and extract it from
DT blob.
Cc: Benoit Cousson
Signed-off-by: Rajendra Nayak
Signed-off-by: Santosh Shil
From: Lokesh Vutla
Add watchdog timer dt node for OMAP5 devices.
Signed-off-by: Lokesh Vutla
Signed-off-by: Santosh Shilimkar
---
arch/arm/boot/dts/omap5.dtsi |7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index 59e05c
OMAP L3 driver needs reg address space for its operation and
hence its a required property.
Cc: Benoit Cousson
Signed-off-by: Santosh Shilimkar
---
.../devicetree/bindings/arm/omap/l3-noc.txt|1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/om
Add missing OMAP keypad reg property information.
Cc: Benoit Cousson
Signed-off-by: Santosh Shilimkar
---
arch/arm/boot/dts/omap5.dtsi |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index ff09720..e539258 100644
--- a/arch/arm
GIC is not part of OCP space so move the gic dt node out of ocp
dt address space.
Cc: Benoit Cousson
Signed-off-by: Santosh Shilimkar
---
arch/arm/boot/dts/omap5.dtsi | 19 +++
1 file changed, 11 insertions(+), 8 deletions(-)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/
It has been decided to not duplicate banked modules dt nodes and that is
how the current arch timer dt extraction code is.
Update the OMAP5 dt file accordingly.
Cc: Benoit Cousson
Signed-off-by: Santosh Shilimkar
---
arch/arm/boot/dts/omap5.dtsi | 19 +++
1 file changed, 7 i
To be able to run kernel in HYP mode, virtual timer and gic node information
needs to be popullated.
Cc: Benoit Cousson
Signed-off-by: Santosh Shilimkar
---
arch/arm/boot/dts/omap5.dtsi |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/omap5.dtsi
From: Rajendra Nayak
Specify both secure as well as nonsecure PPI IRQ for arch
timer. This fixes the following errors seen on DT OMAP5 boot..
[0.00] arch_timer: No interrupt available, giving up
Cc: Benoit Cousson
Signed-off-by: Rajendra Nayak
Signed-off-by: Santosh Shilimkar
---
a
On OMAP5 to detect invalid/bad memory accesses, 16MB of DDR is used as a trap.
Hence available memory for linux OS is 2032 MB on boards popullated with 2 GB
memory.
Cc: Benoit Cousson
Signed-off-by: Santosh Shilimkar
---
arch/arm/boot/dts/omap5-evm.dts |2 +-
1 file changed, 1 insertion(+)
Benoit,
Here is the branch rebased and updated against your 'for_3.10/dt' branch.
Few minor updates about ocp/l3 node after our discussion at connect from
last version. The series also contains couple of hwmod patches to deal
with ocp address space from dt blob and avoiding iormap for some of
the
> "Daniel" == Daniel Mack writes:
Hi,
>> I know this patch reintroduces bits that have been intentionally
>> removed before, in particular by 032ec49f53 ("usb: musb: drop
>> useless board_mode usage"), but I don't know how this usb driver is
>> supposed to work in host mode without takin
On 2013-03-19 12:07, Paul Bolle wrote:
> The only user of Kconfig symbol FB_OMAP_CONSISTENT_DMA_SIZE got removed
> in v3.8, with commit 6ba54ab4a49bbad736b0254aa6bdf0cb83013815 ("ARM:
> OMAP: Remove omap_init_consistent_dma_size()"). Remove this symbol too.
>
> Signed-off-by: Paul Bolle
> ---
>
On 2013-03-19 08:45, Archit Taneja wrote:
> I was trying to come up with a macro which could add default ops to the
> omap_dss_driver. It isn't straight forward as I thought, because you
> need to choose either the default op, or the panel driver's op if it
> exists. For example, I can't create a
On 08.03.2013 17:44, Daniel Mack wrote:
> On 07.03.2013 13:51, Daniel Mack wrote:
>> On 04.03.2013 00:53, Daniel Mack wrote:
>>> Hi Peter,
>>>
>>> On 03.03.2013 23:24, Peter Korsgaard wrote:
> "Daniel" == Daniel Mack writes:
Hi,
Daniel> On my board, the USB is purely u
Hi Grant,
On Mar 16, 2013, at 11:24 AM, Grant Likely wrote:
> On Wed, 23 Jan 2013 12:58:02 +0200, Pantelis Antoniou
> wrote:
>> Hi David,
>>
>> On Jan 23, 2013, at 6:40 AM, David Gibson wrote:
>>> Ok. Nonetheless it's not hard to avoid a recursive approach here.
>>
>> How can I find the maxi
Hi Grant,
The 3rd patch is in preparation for some patches I have in WIP that would allow
drivers to set notifications for properties that are changed in runtime.
I think that since you have the all configuration taking place via DT and you
have a method to alter DT properties in run-time via /pr
clk inits on OMAP happen quite early, even before slab is available.
The dependency comes from the fact that the timer init code starts to
use clocks and hwmod and we need clocks to be initialized by then.
There are various problems doing clk inits this early, one is,
not being able to do dynamic
On Tue, Mar 19, 2013 at 06:39:38AM +, Santosh Shilimkar wrote:
> On Monday 18 March 2013 10:36 PM, Will Deacon wrote:
> > Any chance you could follow up with your firmware/hardware guys about this
> > please? I'd really like to understand how we end up in this state in case we
> > can do someth
The only user of Kconfig symbol FB_OMAP_CONSISTENT_DMA_SIZE got removed
in v3.8, with commit 6ba54ab4a49bbad736b0254aa6bdf0cb83013815 ("ARM:
OMAP: Remove omap_init_consistent_dma_size()"). Remove this symbol too.
Signed-off-by: Paul Bolle
---
Eyeball tested only.
drivers/video/omap/Kconfig | 11
On Tue, 2013-03-19 at 14:21 +0530, Santosh Shilimkar wrote:
> + Tero,
>
> On Monday 18 March 2013 09:08 PM, Paul Walmsley wrote:
> >
> > Here are some basic OMAP test results for Linux v3.9-rc3.
> > Logs and other details at:
> >
> > http://www.pwsan.com/omap/testlogs/test_v3.9-rc3/201303140
1 - 100 of 101 matches
Mail list logo
