Hi Hans, Laurent,
On Friday 06 September 2013 03:42 PM, Archit Taneja wrote:
VPE(Video Processing Engine) is an IP found on DRA7xx, this series adds VPE as a
mem to mem v4l2 driver, and VPDMA as a helper library.
The first version of the patch series described VPE in detail, you can have a
look
Currently, omapdrm, omapfb and omap_vout platform devices are created and
registered through omap_arch_initcalls. In a multiplatform config. It's
possible that all the corresponding configs for the above drivers along with
omapdss config are selected even if the hardware doesn't have a DSS IP.
If
Move omapdrm device creation inside the omap_display_init so that we can
correctly create the device based on the presence of omapdss within the
platform.
For example, on a kernel image supporting multiple platforms, omap_init_drm
will create a omapdrm platform device on a AM33xx platform even tho
DMM exists on omap4+ platforms, these platforms are always expected to boot with
DT. Remove the current method of searching the dmm hwmod and building an
omap_device for dmm.
For OMAP4, the address and irq data for DMM hwmod(along with other blocks) were
removed, so the current method fails in the
Move omapfb and omapvrfb device creation inside the omap_display_init so that
we can correctly create the device based on the presence of omapdss within the
platform.
For example, on a kernel image supporting multiple platforms, omap_init_vrfb and
omap_init_fb will create omapvrfb and omapfb platf
Move omap_vout device creation inside the omap_display_init so that we can
correctly create the device based on the presence of omapdss within the
platform.
For example, on a kernel image supporting multiple platforms, omap_init_vout
will create a omapdrm platform device on a AM33xx platform even
Hi,
On 09/16/2013 05:52 AM, Kishon Vijay Abraham I wrote:
> On Thursday 12 September 2013 06:49 PM, Roger Quadros wrote:
>> On 09/02/2013 06:43 PM, Kishon Vijay Abraham I wrote:
>>> Adapted dwc3 core to use the Generic PHY Framework. So for init, exit,
>>> power_on and power_off the following APIs
On 09/16/2013 06:01 AM, Kishon Vijay Abraham I wrote:
> On Thursday 12 September 2013 04:49 PM, Roger Quadros wrote:
>> Hi Kishon,
>>
>> On 09/02/2013 06:43 PM, Kishon Vijay Abraham I wrote:
>>> Adapted omap-usb3 PHY driver to Generic PHY Framework and moved
>>> phy-omap-usb3
>>> driver in drivers
Hi,
On Thu, Sep 12, 2013 at 6:41 PM, Roger Quadros wrote:
> On 09/12/2013 02:26 PM, Vivek Gautam wrote:
>> Hi,
>>
>>
>> On Thu, Sep 12, 2013 at 4:34 PM, Roger Quadros wrote:
>>> Hi,
>>>
>>> On 09/12/2013 01:47 PM, Vivek Gautam wrote:
On Thu, Sep 12, 2013 at 4:06 PM, Roger Quadros wrote:
>
On 16/09/13 10:18, Archit Taneja wrote:
> Currently, omapdrm, omapfb and omap_vout platform devices are created and
> registered through omap_arch_initcalls. In a multiplatform config. It's
> possible that all the corresponding configs for the above drivers along with
> omapdss config are selected
The DMM/Tiler block can used by omapdrm to allocate frame buffers. With the
removal of address and irq data from the omap4 hwmods, the probe of DMM driver
fails and omapdrm isn't able to utilize the DMM hardware.
Add DMM bindings for omap4 and omap5.
Changes in v2:
- No changes, split out into a
Add Dynamic Memory Manager (DMM) bindings for OMAP4 and OMAP5 devices. DMM
only requires address and irq information.
Add documentation for the DMM bindings.
Originally worked on by Andy Gross.
Cc: Andy Gross
Signed-off-by: Archit Taneja
---
Documentation/devicetree/bindings/arm/omap/dmm.txt
Enable use of DT for DMM/Tiler.
Originally worked on by Andy Gross.
Cc: Andy Gross
Cc: DRI Development
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/omapdrm/omap_dmm_tiler.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/gpu/drm/omapdrm/omap_dmm_tiler.c
b/drivers
On 12/09/13 11:42, Sathya Prakash M R wrote:
> While using HDMI connector driver with sil9022 encoder
> came across issue where connector driver is probed first.
> This resulted in error. A deffered probe solved this.
> Most connector drivers need a encoder driver as their
> video source. This patc
Hi Dear !
How are you doing today,hope fine,My name is Chandrine Ahmed Abdalla and i am a
girl. I will be very glad if you can contact me through my email address,
and i will tell you more about myself here is my
adress(chandrine.abda...@hotmail.com)
Remember the distance,color or age does not m
On 16/09/13 12:30, Archit Taneja wrote:
> Add Dynamic Memory Manager (DMM) bindings for OMAP4 and OMAP5 devices. DMM
> only requires address and irq information.
>
> Add documentation for the DMM bindings.
>
> Originally worked on by Andy Gross.
>
> Cc: Andy Gross
> Signed-off-by: Archit Taneja
On 16/09/13 12:30, Archit Taneja wrote:
> The DMM/Tiler block can used by omapdrm to allocate frame buffers. With the
> removal of address and irq data from the omap4 hwmods, the probe of DMM driver
> fails and omapdrm isn't able to utilize the DMM hardware.
>
> Add DMM bindings for omap4 and omap
Hi Joel,
On Saturday 14 September 2013 06:27 AM, Joel Fernandes wrote:
> From: Joel Fernandes
> Subject: [PATCH v4] ARM: EDMA: Fix clearing of unused list for DT DMA
> resources
>
> HWMOD removal for MMC is breaking edma_start as the events are being manually
> triggered due to unused channel l
On Mon, Sep 16, 2013 at 2:28 AM, Archit Taneja wrote:
> On Friday 13 September 2013 07:44 PM, Rob Clark wrote:
>>
>> On Fri, Sep 13, 2013 at 5:14 AM, Archit Taneja wrote:
>>>
>>> Enable use of DT for DMM/Tiler.
>>>
>>> Originally worked on by Andy Gross.
>>
>>
>> looks good.. but do we want to ge
On Friday 13 September 2013 09:07 PM, Tony Lindgren wrote:
> * Sekhar Nori [130913 03:18]:
>> Get rid of TI specific binding ti,non-removable in favour of the
>> generic binding present for the same purpose.
>
> Looks like there's a different handling in the MMC driver
> for no_regulator_off_init
On Monday 16 September 2013 04:49 PM, Tomi Valkeinen wrote:
On 16/09/13 12:30, Archit Taneja wrote:
Add Dynamic Memory Manager (DMM) bindings for OMAP4 and OMAP5 devices. DMM
only requires address and irq information.
Add documentation for the DMM bindings.
Originally worked on by Andy Gross.
On Saturday 14 September 2013 03:37 AM, Balaji T K wrote:
> On Friday 13 September 2013 09:07 PM, Tony Lindgren wrote:
>> * Sekhar Nori [130913 03:18]:
>>> Get rid of TI specific binding ti,non-removable in favour of the
>>> generic binding present for the same purpose.
>>
>> Looks like there's a
On Sun, Sep 15, 2013 at 10:44 PM, Sebastian Reichel wrote:
> Add SSI device tree data for OMAP34xx and Nokia N900.
>
> Signed-off-by: Sebastian Reichel
> ---
> Documentation/devicetree/bindings/hsi/omap_ssi.txt | 73
> ++
> arch/arm/boot/dts/omap3-n900.dts
On 22:44-20130915, Sebastian Reichel wrote:
> Add SSI device tree data for OMAP34xx and Nokia N900.
>
> Signed-off-by: Sebastian Reichel
> ---
> Documentation/devicetree/bindings/hsi/omap_ssi.txt | 73
> ++
> arch/arm/boot/dts/omap3-n900.dts | 8 +++
> arc
On 10:49-20130916, Aida Mynzhasova wrote:
> On 24.08.2013 18:02, Aida Mynzhasova wrote:
> >This patch adds required definitions and structures for clockdomain
> >initialization, so omap3xxx_clockdomains_init() was substituted by
> >new ti81xx_clockdomains_init() while ea
Hi Paul, Benoit,
This series adds PRCM support for AM43x SoC's. It has been modified
as compared to last version based on Rajendra's comments and discussion
with him, please let me know your comments on this series.
Major changes (as compared to v2):
1. omap_hwmod_33xx_43xx_interconnect_data.c ha
From: Ankur Kishore
Most of the AM43x CM reg address offsets are with MSB bit '1' (on
16-bit value) leading to arithmetic miscalculations while calculating
CLOCK ENABLE register's address because cm_inst field was a type of
"const s16", so make it "const u16".
Also modify relevant functions so a
Add AM43x CMINST, CDOFFS, RM_RSTST & RM_RSTCTRL definitions - minimal
ones that would be used.
Signed-off-by: Afzal Mohammed
---
arch/arm/mach-omap2/prcm43xx.h | 141 +
1 file changed, 141 insertions(+)
create mode 100644 arch/arm/mach-omap2/prcm43xx.h
d
Hwmod common to AM43x and AM335x has register offsets different. It is
now updated based on SoC detection at run time, hence remove statically
initialized ones.
Signed-off-by: Afzal Mohammed
---
.../mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c | 50 --
1 file changed, 50 de
Most of IP's in AM335x is present on AM43x and so in those cases both
will use same hwmod database (except for a few cases where clock related
details differ), but there is difference w.r.t register offset between
these. Update register offsets at runtime based on the SoC detected to
help in sharin
AM335x and AM43x have most of the interconnect's similar. Instead of
adding redundant hwmod data, move interconnects similar between AM335x
and AM43x to a common location. This helps in reuse on AM43x.
AM335x interconnects that has difference and not present in AM43x is
not moved. Ocp clock of tho
Add hwmod support for IP's that are present in AM43x, but not in AM335x.
AM43x additional ones added here are,
1. synctimer
2. timer8-11
3. ehrpwm3-5
4. spi2-4
5. gpio4-5
AM43x pruss interconnect which is different as compared to AM335x, has
been taken care.
And register offsets for same hwmod's
From: Ambresh K
Initialise AM43x HWMOD, powerdomains and clockdomains.
Signed-off-by: Ambresh K
Signed-off-by: Afzal Mohammed
---
arch/arm/mach-omap2/io.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/mach-omap2/io.c b/arch/arm/mach-omap2/io.c
index ff2113c..c90f647 10064
Build AM43x power domain, clock domain and hwmod data.
Many of AM43x IP's and interconnects are similar as that in AM335x,
hence AM335x hwmod data is being reused with necessary changes.
Earlier the plan was to reuse AM335x specific PRCM code, but as AM43x
PRCM register layout is much similar to
Reuse OMAP4 operations on AM43x.
Signed-off-by: Ambresh K
Signed-off-by: Afzal Mohammed
---
arch/arm/mach-omap2/omap_hwmod.c | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/mach-omap2/omap_hwmod.c b/arch/arm/mach-omap2/omap_hwmod.c
index d9ee0ff..aa593da 100644
--- a/arch/a
From: Ambresh K
Add the data file to describe all power domains in AM43x SoC.
OMAP4 powerdomain operations is being reused here.
Signed-off-by: Ambresh K
Signed-off-by: Afzal Mohammed
---
arch/arm/mach-omap2/powerdomain.h | 1 +
arch/arm/mach-omap2/powerdomains43xx_data.c | 145 ++
From: Ambresh K
Add the data file to describe clock domains in AM43x SoC.
OMAP4 clockdomain operations is being reused here.
Signed-off-by: Ambresh K
Signed-off-by: Afzal Mohammed
---
arch/arm/mach-omap2/clockdomain.h | 2 +
arch/arm/mach-omap2/clockdomains43xx_data.c | 199 ++
Hi,
> Is the Synchronous Serial Interface (SSI) only supported by
> OMAP34xx/OMAP35xx SoC and not by OMAP36xx/OMAP37xx SoC?
>
> I'm asking this since if SSI is supported by both we should add the
> device nodes in omap3.dtsi instead of omap34xx.dtsi.
>
> I thought that all OMAP3 SoC supported S
On 09/16/2013 08:48 AM, Afzal Mohammed wrote:
> From: Ambresh K
>
> Add the data file to describe clock domains in AM43x SoC.
> OMAP4 clockdomain operations is being reused here.
>
> Signed-off-by: Ambresh K
> Signed-off-by: Afzal Mohammed
> ---
> arch/arm/mach-omap2/clockdomain.h |
On 09/16/2013 06:48 AM, Sekhar Nori wrote:
> Hi Joel,
>
> On Saturday 14 September 2013 06:27 AM, Joel Fernandes wrote:
>> From: Joel Fernandes
>> Subject: [PATCH v4] ARM: EDMA: Fix clearing of unused list for DT DMA
>> resources
>>
>> HWMOD removal for MMC is breaking edma_start as the events a
On Sat, Sep 14, 2013 at 10:37:12AM +0100, Pali Rohár wrote:
> On Sunday 08 September 2013 09:43:29 Pali Rohár wrote:
> > Here is new version (v4) of omap secure part patch:
> >
> > Other secure functions omap_smc1() and omap_smc2() calling
> > instruction smc #0 but Nokia RX-51 board needs to call
On Sat, Sep 14, 2013 at 7:19 AM, Frederic Weisbecker wrote:
> On Fri, Sep 13, 2013 at 03:50:07PM -0700, Kevin Hilman wrote:
>> Frederic Weisbecker writes:
>>
>> > On Tue, Sep 10, 2013 at 08:07:45AM -0700, Kevin Hilman wrote:
>> >> Nicolas Pitre writes:
>> >>
>> >> > Adding Kevin Hilman to the CC
On Mon, Sep 16, 2013 at 5:01 PM, Sebastian Reichel wrote:
> Hi,
>
>> Is the Synchronous Serial Interface (SSI) only supported by
>> OMAP34xx/OMAP35xx SoC and not by OMAP36xx/OMAP37xx SoC?
>>
>> I'm asking this since if SSI is supported by both we should add the
>> device nodes in omap3.dtsi inste
Hi,
On Mon, Sep 16, 2013 at 05:01:47PM +0200, Sebastian Reichel wrote:
> > Is the Synchronous Serial Interface (SSI) only supported by
> > OMAP34xx/OMAP35xx SoC and not by OMAP36xx/OMAP37xx SoC?
> >
> > I'm asking this since if SSI is supported by both we should add the
> > device nodes in omap3
Quoting Tero Kristo (2013-09-13 04:34:54)
> On 09/13/2013 10:51 AM, Stefan Roese wrote:
> > On 11.09.2013 09:21, Tomi Valkeinen wrote:
> >> On 10/09/13 16:17, Tero Kristo wrote:
> >>
> >>> In theory, DPLLs can also be used in their bypass mode to feed customer
> >>> nodes clocks. I just think the c
On Mon, Sep 16, 2013 at 09:10:32PM +0300, Aaro Koskinen wrote:
> On Mon, Sep 16, 2013 at 05:01:47PM +0200, Sebastian Reichel wrote:
> > > Is the Synchronous Serial Interface (SSI) only supported by
> > > OMAP34xx/OMAP35xx SoC and not by OMAP36xx/OMAP37xx SoC?
> > >
> > > I'm asking this since if
* Olof Johansson [130913 22:17]:
> Hi,
>
> Not related to wlan but with DT conversion; I noticed the following in
> dmesg on Panda ES with omap2plus_defconfig on current mainline:
>
> [0.00] smp_twd: clock not found -2
That should get fixed for v3.13 when we get the proper DT clocks
for
This adds the interrupt configuration for the
Cortex-A15 GIC to make KVM work in HYP mode
---
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 07be2cd..8026a4e 100644
--- a/arch/arm/bo
Hello,
this patch adds the interrupts definition to the Cortex A15
GIC description in the .dtsi the way it's done for most other
A15 cores. This makes KVM work in HYP mode on the OMAP5432 board.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to maj
On Monday 16 September 2013 07:17 PM, Alexander Tarasikov wrote:
> This adds the interrupt configuration for the
> Cortex-A15 GIC to make KVM work in HYP mode
> ---
> arch/arm/boot/dts/omap5.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/boot/dts/omap5.dtsi b/a
On Monday 16 September 2013 09:56 PM, Joel Fernandes wrote:
> On 09/16/2013 06:48 AM, Sekhar Nori wrote:
>> Hi Joel,
>>
>> On Saturday 14 September 2013 06:27 AM, Joel Fernandes wrote:
>>> From: Joel Fernandes
>>> Subject: [PATCH v4] ARM: EDMA: Fix clearing of unused list for DT DMA
>>> resources
On 09/17/2013 12:08 AM, Sekhar Nori wrote:
[..]
>>> I still cannot find any users of edma in the device tree sources either
>>> in linux-next or linus/master. Why cannot this wait until v3.13?
>>
>> I understand this affects only DT users of EDMA. But I get so many private
>> reports of breakage du
On Tuesday 17 September 2013 11:08 AM, Joel Fernandes wrote:
> On 09/17/2013 12:08 AM, Sekhar Nori wrote:
> [..]
I still cannot find any users of edma in the device tree sources either
in linux-next or linus/master. Why cannot this wait until v3.13?
>>>
>>> I understand this affects only
On Tue, 2013-09-17 at 09:26 +0300, Luca Coelho wrote:
> Both patches look good to me, though I didn't have the time to retest
> them.
Actually I don't even have a Blaze device anymore, so I can't really
test the second patch. :(
--
Luca.
--
To unsubscribe from this list: send the line "unsubscri
Hi Tony,
Both patches look good to me, though I didn't have the time to retest
them.
--
Cheers,
Luca.
On Fri, 2013-09-13 at 12:09 -0700, Tony Lindgren wrote:
> Commit b42b9181 (ARM: OMAP2+: Remove board-omap4panda.c)
> removed legacy booting in favor of device tree based booting
> for pandaboard
55 matches
Mail list logo
