From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Christoph Fritz <chf.fritz@googlemail.com>
Cc: Dave Airlie <airlied@gmail.com>,
linux-omap <linux-omap@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] OMAPDSS: DPI: add dependency to DSI
Date: Thu, 18 Apr 2013 17:37:45 +0300 [thread overview]
Message-ID: <51700539.7080603@ti.com> (raw)
In-Reply-To: <1366280026.4085.55.camel@mars>
[-- Attachment #1: Type: text/plain, Size: 1785 bytes --]
On 2013-04-18 13:13, Christoph Fritz wrote:
> On Thu, 2013-04-18 at 12:21 +0300, Tomi Valkeinen wrote:
>> On 2013-04-18 12:09, Tomi Valkeinen wrote:
>>> On 2013-04-18 11:37, Christoph Fritz wrote:
>>
>>>> With linux-next this patch breaks compiling here because DPI now depends
>>>> on DSI - but my omap3 board here doesn't use DSI at all:
>>>>
>>>> drivers/video/omap2/dss/dpi.c: In function ‘dpi_calc_pll_cb’:
>>>> drivers/video/omap2/dss/dpi.c:181: error: implicit declaration of function ‘dsi_hsdiv_calc’
>>>> drivers/video/omap2/dss/dpi.c: In function ‘dpi_dsi_clk_calc’:
>>>> drivers/video/omap2/dss/dpi.c:201: error: implicit declaration of function ‘dsi_get_pll_clkin’
>>>> drivers/video/omap2/dss/dpi.c:212: error: implicit declaration of function ‘dsi_pll_calc’
>>>>
>>>> Enabling OMAP2_DSS_DSI fixes this. This is my proposed patch. You may be want to merge it?
>>>
>>> Thanks for reporting this. We shouldn't make DPI depend on DSI. We
>>> should make dummy functions for the above when DSI is not enabled so
>>> that DPI compiles. I'll make a fix.
>>
>> Patch below. Can you try it out? It works for me on Panda.
>
> Thanks, it compiles here fine too.
>
> and while booting I'm now getting as with 3.9-rc:
> [ 0.409729] OMAP DSS rev 2.0
> [ 0.410980] omapdss DPI error: can't get VDDS_DSI regulator
> [ 0.410980] omapdss DPI error: device ips-056t init failed: -517
>
> But here with linux-next (in contrast to 3.9-rc) removing all regulator
> dependencies from drivers/video/omap2/dss/dpi.c does not make the trick.
> The display stays dark :-( ...
That's with your DT hacked kernel, right? Not the official supported one.
I don't think anything changed related to regulators in omapdss.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
next prev parent reply other threads:[~2013-04-18 14:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 10:57 [GIT PULL] omap display changes for 3.10 Tomi Valkeinen
2013-04-18 8:37 ` [PATCH] OMAPDSS: DPI: add dependency to DSI Christoph Fritz
2013-04-18 9:09 ` Tomi Valkeinen
2013-04-18 9:21 ` Tomi Valkeinen
2013-04-18 10:13 ` Christoph Fritz
2013-04-18 14:37 ` Tomi Valkeinen [this message]
2013-04-18 17:26 ` Christoph Fritz
2013-04-22 11:51 ` Tomi Valkeinen
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=51700539.7080603@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=airlied@gmail.com \
--cc=chf.fritz@googlemail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-omap@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).