From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "Taneja, Archit" <archit@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 4/4] OMAP: DSS2: Check for SDI HW before accessing SDI registers
Date: Tue, 1 Mar 2011 09:38:37 +0200 [thread overview]
Message-ID: <1298965117.2011.17.camel@deskari> (raw)
In-Reply-To: <4D6C96E9.20206@ti.com>
On Tue, 2011-03-01 at 00:49 -0600, Taneja, Archit wrote:
> Hi,
>
> On Thursday 24 February 2011 07:04 PM, Valkeinen, Tomi wrote:
> > Only OMAP 3430 hardware has SDI support. The availability of SDI HW can
> > be found out by checking if the LCD channel supports SDI displays.
> >
> > This patch checks for SDI HW support before accessing SDI registers,
> > which fixes a crash on OMAP4 when SDI SW support is compiled in.
> >
> > Signed-off-by: Tomi Valkeinen<tomi.valkeinen@ti.com>
> > ---
> > drivers/video/omap2/dss/display.c | 10 ++++++++++
> > drivers/video/omap2/dss/dss.c | 29 ++++++++++++++++++-----------
> > 2 files changed, 28 insertions(+), 11 deletions(-)
> >
> > diff --git a/drivers/video/omap2/dss/display.c b/drivers/video/omap2/dss/display.c
> > index 3f4fa0b..58459f4 100644
> > --- a/drivers/video/omap2/dss/display.c
> > +++ b/drivers/video/omap2/dss/display.c
> > @@ -30,6 +30,7 @@
> >
> > #include<plat/display.h>
> > #include "dss.h"
> > +#include "dss_features.h"
> >
> > static LIST_HEAD(display_list);
> >
> > @@ -392,6 +393,15 @@ void dss_init_device(struct platform_device *pdev,
> > struct device_attribute *attr;
> > int i;
> > int r;
> > + enum omap_display_type supported;
> > +
> > + supported = dss_feat_get_supported_displays(dssdev->channel);
> > +
> > + if (!(supported& dssdev->type)) {
> > + DSSERR("Unsupported display interface for display '%s'.\n",
> > + dssdev->name);
> > + return;
> > + }
>
> This would make it necessary to specify the channel in the board file,
> especially digit. I think this patch should also add the channel
> parameters for all board files which add a tv display.
Argh. You're right, dssdev->channel is not what I thought it is. That is
rather confusing. I remember this was discussed when that
dssdev->channel was introduced.
I believe this should work if I change dssdev->channel to
dssdev->manager->id.
But this dssdev->channel has to be fixed somehow, I'm 100% sure this
won't be the last time somebody tries to use it =).
Tomi
next prev parent reply other threads:[~2011-03-01 7:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 13:34 [PATCH 1/4] OMAP: DSS2: Clean up a switch-case Tomi Valkeinen
2011-02-24 13:34 ` [PATCH 2/4] OMAP: DSS2: FEATURES: Remove SDI from 3630 displays Tomi Valkeinen
2011-02-24 13:34 ` [PATCH 3/4] OMAP: DSS2: FEATURES: Remove DSI & SDI from OMAP2 Tomi Valkeinen
2011-02-25 5:06 ` archit taneja
2011-02-24 13:34 ` [PATCH 4/4] OMAP: DSS2: Check for SDI HW before accessing SDI registers Tomi Valkeinen
2011-03-01 6:49 ` archit taneja
2011-03-01 7:38 ` Tomi Valkeinen [this message]
2011-03-01 7:46 ` archit taneja
2011-03-01 8:00 ` Tomi Valkeinen
2011-03-01 8:32 ` archit taneja
2011-03-01 7:42 ` 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=1298965117.2011.17.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=archit@ti.com \
--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