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 check in the clkoutx2_recalc is wrong,
and should be enhanced to actually check what is the target mode for
Move omapdrm device creation inside the omap_display_init so that we can
correctly create the device based on the presence of omapdss.
Originally worked on by Andy Gross.
Cc: Andy Gross andy...@gmail.com
Signed-off-by: Archit Taneja arc...@ti.com
---
arch/arm/mach-omap2/Makefile | 4 ---
Enable use of DT for DMM/Tiler.
Originally worked on by Andy Gross.
Cc: Andy Gross andy...@gmail.com
Cc: DRI Development dri-de...@lists.freedesktop.org
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/gpu/drm/omapdrm/omap_dmm_tiler.c | 11 +++
1 file changed, 11 insertions(+)
DMM exists on omap4+ platforms, these platforms will always boot with DT. Remove
the previous method of searching the dmm hwmod and building the device by
ourselves. Addition of a DMM nodes in DT will ensure a DMM device is built.
For OMAP4, the address and irq data for most hwmods were removed,
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 andy...@gmail.com
Signed-off-by: Archit Taneja arc...@ti.com
---
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. Also, make sure DRM device is built only
when
Op 13 sep. 2013, om 00:27 heeft Kevin Hilman khil...@linaro.org het volgende
geschreven:
Koen Kooi k...@dominion.thruhere.net writes:
Here are two patches to fix MMC on beaglebone, one fixes card detect on BBW,
the other adds the eMMC entry for BBB and its fixed regulator. After that
On 13/09/13 12:14, Archit Taneja wrote:
Move omapdrm device creation inside the omap_display_init so that we can
correctly create the device based on the presence of omapdss.
Originally worked on by Andy Gross.
If the dmm device is present in the DT data, there is no need to create
the dmm
On 13/09/13 12:14, Archit Taneja wrote:
DMM exists on omap4+ platforms, these platforms will always boot with DT.
Remove
the previous method of searching the dmm hwmod and building the device by
ourselves. Addition of a DMM nodes in DT will ensure a DMM device is built.
For OMAP4, the
On Friday 13 September 2013 02:54 PM, Tomi Valkeinen wrote:
On 13/09/13 12:14, Archit Taneja wrote:
Move omapdrm device creation inside the omap_display_init so that we can
correctly create the device based on the presence of omapdss.
Originally worked on by Andy Gross.
If the dmm device is
On Friday 13 September 2013 03:08 PM, Archit Taneja wrote:
On Friday 13 September 2013 02:54 PM, Tomi Valkeinen wrote:
On 13/09/13 12:14, Archit Taneja wrote:
Move omapdrm device creation inside the omap_display_init so that we can
correctly create the device based on the presence of omapdss.
On 13/09/13 12:38, Archit Taneja wrote:
Also, omapfb device is currently created the same way as omapdrm,
independently of omapdss. Why is it a problem to have them like that?
In a multiplatform config, we might have CONFIG_DRM_OMAP and
CONFIG_DRM_OMAP_MODULE selected.
This would cause
On 13/09/13 12:39, Archit Taneja wrote:
On Friday 13 September 2013 03:08 PM, Archit Taneja wrote:
On Friday 13 September 2013 02:54 PM, Tomi Valkeinen wrote:
On 13/09/13 12:14, Archit Taneja wrote:
Move omapdrm device creation inside the omap_display_init so that we
can
correctly create the
On Friday 13 September 2013 03:18 PM, Tomi Valkeinen wrote:
On 13/09/13 12:39, Archit Taneja wrote:
On Friday 13 September 2013 03:08 PM, Archit Taneja wrote:
On Friday 13 September 2013 02:54 PM, Tomi Valkeinen wrote:
On 13/09/13 12:14, Archit Taneja wrote:
Move omapdrm device creation
On 13/09/13 12:51, Archit Taneja wrote:
The calls in omap_generic_init() check the machine type via
of_machine_is_compatible(), even if it's a multiplatform image, the dtb
should be only of one platform. So it wouldn't be called at all.
Hmm. BeagleBone is ti,am33xx. The Generic AM33XX
Get rid of TI specific binding ti,non-removable in favour of the
generic binding present for the same purpose.
This patch set does not support the old binding anymore. So, yes,
it does introduce an ABI breakage. IMHO, it is not really worth
supporting both bindings ATM since DT-usage in OMAP is
Remove the vendor specific ti,non-removable DT binding and
support the generic binding non-removable instead.
Signed-off-by: Sekhar Nori nsek...@ti.com
---
Documentation/devicetree/bindings/mmc/ti-omap-hsmmc.txt |5 ++---
drivers/mmc/host/omap_hsmmc.c |2 +-
2
Mark the eMMC module on BeagleBone black as non removable.
Signed-off-by: Sekhar Nori nsek...@ti.com
---
arch/arm/boot/dts/am335x-boneblack.dts |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/am335x-boneblack.dts
b/arch/arm/boot/dts/am335x-boneblack.dts
index
The TI specific binding for non-removable cards is now gone.
The driver supports the generic binding, start using it.
Signed-off-by: Sekhar Nori nsek...@ti.com
---
arch/arm/boot/dts/omap4-panda-common.dtsi |2 +-
arch/arm/boot/dts/omap4-sdp.dts |4 ++--
Op 13 sep. 2013, om 12:09 heeft Sekhar Nori nsek...@ti.com het volgende
geschreven:
Mark the eMMC module on BeagleBone black as non removable.
Signed-off-by: Sekhar Nori nsek...@ti.com
Acked-by: Koen Kooi k...@dominion.thruhere.net
---
arch/arm/boot/dts/am335x-boneblack.dts |1 +
1
On Friday 13 September 2013 03:32 PM, Tomi Valkeinen wrote:
On 13/09/13 12:51, Archit Taneja wrote:
The calls in omap_generic_init() check the machine type via
of_machine_is_compatible(), even if it's a multiplatform image, the dtb
should be only of one platform. So it wouldn't be called at
On 13/09/13 13:17, Archit Taneja wrote:
On Friday 13 September 2013 03:32 PM, Tomi Valkeinen wrote:
On 13/09/13 12:51, Archit Taneja wrote:
The calls in omap_generic_init() check the machine type via
of_machine_is_compatible(), even if it's a multiplatform image, the dtb
should be only of
These patches complete the OMAP4 HDMI register definitions for HDMI submodules
and make sure all the corresponding regdump functions dump all the registers.
Ricardo Neri (7):
OMAPDSS: HDMI: OMAP4: Complete register definitions for wrapper
OMAPDSS: HDMI: OMAP4: Complete dumping of wrapper
From: Ricardo Neri ricardo.n...@ti.com
Add definitions for missing registers in the HDMI wrapper. Also, order
the registers by offset to improve readability.
Signed-off-by: Ricardo Neri ricardo.n...@ti.com
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/video/omap2/dss/ti_hdmi_4xxx_ip.h
From: Ricardo Neri ricardo.n...@ti.com
Add missing registers when dumping the HDMI wrapper. Also, order the dump by
offset to improve readability.
Signed-off-by: Ricardo Neri ricardo.n...@ti.com
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/video/omap2/dss/ti_hdmi_4xxx_ip.c | 5 -
From: Ricardo Neri ricardo.n...@ti.com
Rename the register to be aligned with the HDMI_CORE_SYS naming convention.
Also, update the naming of the #defines used for its fields.
Signed-off-by: Ricardo Neri ricardo.n...@ti.com
Signed-off-by: Archit Taneja arc...@ti.com
---
From: Ricardo Neri ricardo.n...@ti.com
Add the spread spectrum clock configuration registers to the DPLL dump.
Signed-off-by: Ricardo Neri ricardo.n...@ti.com
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/video/omap2/dss/ti_hdmi_4xxx_ip.c | 2 ++
1 file changed, 2 insertions(+)
diff
From: Ricardo Neri ricardo.n...@ti.com
Add missing register definitions for spread spectrum clocking.
Signed-off-by: Ricardo Neri ricardo.n...@ti.com
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/video/omap2/dss/ti_hdmi_4xxx_ip.h | 2 ++
1 file changed, 2 insertions(+)
diff --git
From: Ricardo Neri ricardo.n...@ti.com
Add missing register entries when dumping the core.
Signed-off-by: Ricardo Neri ricardo.n...@ti.com
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/video/omap2/dss/ti_hdmi_4xxx_ip.c | 47 ++-
1 file changed, 46
From: Ricardo Neri ricardo.n...@ti.com
Add missing register definitions; mainly for colorspace conversion, video
timing and interrupt handling.
Signed-off-by: Ricardo Neri ricardo.n...@ti.com
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/video/omap2/dss/ti_hdmi_4xxx_ip.h | 48
On Friday 13 September 2013 03:54 PM, Tomi Valkeinen wrote:
On 13/09/13 13:17, Archit Taneja wrote:
On Friday 13 September 2013 03:32 PM, Tomi Valkeinen wrote:
On 13/09/13 12:51, Archit Taneja wrote:
The calls in omap_generic_init() check the machine type via
of_machine_is_compatible(), even
On Friday 13 September 2013 03:39 PM, Sekhar Nori wrote:
Mark the eMMC module on BeagleBone black as non removable.
Signed-off-by: Sekhar Nori nsek...@ti.com
The patches which touch dts files are not really following the subject
line conventions. I will fix that and send a v2.
Thanks to
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 check in the clkoutx2_recalc is wrong,
and should be enhanced to
On Fri, Sep 13, 2013 at 5:14 AM, Archit Taneja arc...@ti.com wrote:
Enable use of DT for DMM/Tiler.
Originally worked on by Andy Gross.
looks good.. but do we want to get information about # of LUT's, etc,
from DT? Or did we decide that we can reliably get this from the hw?
I lost track of
On Thu, 12 Sep 2013, Santosh Shilimkar wrote:
On Thursday 12 September 2013 08:26 PM, Thomas Gleixner wrote:
Let me summarize:
- GIC supports up to 160 interrupts
- CROSSBAR supports up to 250 interrupts
- CROSSBAR routes up to 160 out of 250 interrupts to the GIC ones
On Friday 13 September 2013 10:24 AM, Thomas Gleixner wrote:
On Thu, 12 Sep 2013, Santosh Shilimkar wrote:
On Thursday 12 September 2013 08:26 PM, Thomas Gleixner wrote:
Let me summarize:
- GIC supports up to 160 interrupts
- CROSSBAR supports up to 250 interrupts
- CROSSBAR
* Koen Kooi k...@dominion.thruhere.net [130912 11:43]:
The pinmux is specified in am335x-bone-common.dtsi to be reused by the eMMC
cape.
Signed-off-by: Koen Kooi k...@dominion.thruhere.net
---
arch/arm/boot/dts/am335x-bone-common.dtsi | 22 ++
i know we switched to dtb-only booting, but what's happened to wifi?
3.5.x:
flag@flag-desktop:~$ ls -la /sys/bus/platform/devices/wl12xx/
total 0
drwxr-xr-x 5 root root0 set 13 17:26 .
drwxr-xr-x 4 root root0 set 13 17:26 ..
-rw-r--r-- 1 root root 4096 set 13 17:28 bt_coex_state
* Sekhar Nori nsek...@ti.com [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 that's needed for eMMC. That needs to
be sorted out and
On Tue, Sep 10, 2013 at 08:07:45AM -0700, Kevin Hilman wrote:
Nicolas Pitre nicolas.pi...@linaro.org writes:
Adding Kevin Hilman to the CC as he might be interested as well.
Thanks, I'd already noticed this but was distracted getting arm-soc
changes ready for the merge window. Looking
* Paolo Pisati p.pis...@gmail.com [130913 08:43]:
i know we switched to dtb-only booting, but what's happened to wifi?
3.5.x:
flag@flag-desktop:~$ ls -la /sys/bus/platform/devices/wl12xx/
total 0
drwxr-xr-x 5 root root0 set 13 17:26 .
drwxr-xr-x 4 root root0 set 13 17:26 ..
Commit b42b9181 (ARM: OMAP2+: Remove board-omap4panda.c)
removed legacy booting in favor of device tree based booting
for pandaboard. That caused the WLAN to stop working as the
related .dts entries fell through the cracks.
The legacy muxing was setting pulls for GPIO 48 and 49, so let's
keep
Commit 76787b3b (ARM: OMAP2+: Remove board-4430sdp.c)
removed legacy booting in favor of device tree based booting
for 4430sdp. That caused the WLAN to stop working as the
related .dts entries fell through the cracks.
I don't have the 1283 PG 2.21 connectivity device on my 4430sdp,
but the
Hi all,
Looks like these two patches are still missing as I did not
update the kernel on my panda for a while but was testing with
my 4430sdp that does not have the WLAN card..
Regards,
Tony
---
Tony Lindgren (2):
ARM: dts: Fix muxing and regulator for wl12xx on the SDIO bus for
On Friday 13 September 2013 09:07 PM, Tony Lindgren wrote:
* Sekhar Nori nsek...@ti.com [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
Frederic Weisbecker fweis...@gmail.com writes:
On Tue, Sep 10, 2013 at 08:07:45AM -0700, Kevin Hilman wrote:
Nicolas Pitre nicolas.pi...@linaro.org writes:
Adding Kevin Hilman to the CC as he might be interested as well.
Thanks, I'd already noticed this but was distracted getting arm-soc
On 09/12/2013 04:58 AM, Sekhar Nori wrote:
On Wednesday 11 September 2013 12:22 AM, Joel Fernandes wrote:
HWMOD removal for MMC is breaking edma_start as the events are being manually
triggered due to unused channel list not being clear.
[..]
It is better to send one version with all comments
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
and:
[0.440399] omap-gpmc 5000.gpmc: error: clk_get
-Olof
--
To unsubscribe from this list: send the
48 matches
Mail list logo
