From: tomi.valkeinen@ti•com (Tomi Valkeinen)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: OMAP5: DSS hwmod data
Date: Mon, 17 Mar 2014 15:28:51 +0200 [thread overview]
Message-ID: <5326F893.3080607@ti.com> (raw)
In-Reply-To: <5326F71C.1060602@compulab.co.il>
On 17/03/14 15:22, Dmitry Lifshitz wrote:
> Hi Tomi,
>
> Thank you for the feedback.
>
> We have OMAP5 based board with no ESD & Level Translator chip.
> So, I made a quick hack in tpd12s015 driver to skip using un-relevant
> GPIOs.
If you don't have tpd12s015 on your board, don't modify it. Remove it
from your board's dts file totally.
> I've copied DSS DT structure from uEmv board *.dts.
> However the HDMI output is not activate yet.
>
> Here is some debug output:
>
> root at cm-debian:~# dmesg | grep -i dss
> [ 0.040554] omap_hwmod: dss_dispc: cannot be enabled for reset (3)
> [ 0.043135] omap_hwmod: dss_dsi1: cannot be enabled for reset (3)
> [ 0.045725] omap_hwmod: dss_dsi2: cannot be enabled for reset (3)
> [ 0.048311] omap_hwmod: dss_hdmi: cannot be enabled for reset (3)
> [ 0.050888] omap_hwmod: dss_rfbi: cannot be enabled for reset (3)
> [ 0.325392] DSS: set fck to 192000000
> [ 0.325400] DSS: dss_runtime_get
> [ 0.325427] DSS: dss_restore_context
> [ 0.325445] OMAP DSS rev 6.1
> [ 0.325450] DSS: dss_runtime_put
> [ 0.325456] DSS: dss_save_context
> [ 0.325461] DSS: context saved
> [ 0.325707] DSS: dss_restore_context
> [ 0.325711] DSS: context restored
> [ 0.325746] omapdss_dispc 58001000.dispc: OMAP DISPC rev 5.1
> [ 0.325838] DSS: dss_save_context
> [ 0.325843] DSS: context saved
>
>
> I do not use uEvm BSP u-Boot. I'm forking from this source:
> git://git.denx.de/u-boot-ti.git
>
> Perhaps I'm missing some clocks initialization?
> What are the correct bootargs for activating HDMI video output?
HDMI is the only output on the uevm, and if your board is similar, no
boot args are needed. But, of course, you need omapfb or omapdrm to
manage the display.
Tomi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 901 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140317/dcbd20db/attachment.sig>
next prev parent reply other threads:[~2014-03-17 13:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 10:26 [PATCH] ARM: OMAP5: DSS hwmod data Tomi Valkeinen
2014-03-12 10:26 ` [PATCH] ARM: OMAP5: Add omap5 DSS related " Tomi Valkeinen
2014-03-12 10:33 ` [PATCH] ARM: OMAP5: DSS " Tomi Valkeinen
2014-03-16 11:41 ` Dmitry Lifshitz
2014-03-17 6:13 ` Tomi Valkeinen
2014-03-17 13:22 ` Dmitry Lifshitz
2014-03-17 13:28 ` Tomi Valkeinen [this message]
2014-03-17 14:22 ` Dmitry Lifshitz
2014-03-18 5:29 ` Tomi Valkeinen
2014-03-18 8:19 ` Dmitry Lifshitz
2014-03-18 8:37 ` Tomi Valkeinen
2014-03-18 12:23 ` Dmitry Lifshitz
2014-05-08 4:37 ` Paul Walmsley
2014-05-08 5:48 ` Archit Taneja
2014-05-08 16:01 ` Paul Walmsley
2014-05-09 6:19 ` Archit Taneja
2014-05-09 6:36 ` Tomi Valkeinen
2014-05-14 19:44 ` Paul Walmsley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5326F893.3080607@ti.com \
--to=tomi.valkeinen@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox