From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: "ext Taneja, Archit" <archit@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Semwal, Sumit" <sumit.semwal@ti.com>,
"Mittal, Mukund" <mmittal@ti.com>,
"Nilofer, Samreen" <samreen@ti.com>
Subject: RE: [PATCH v5 3/7] OMAP: DSS2: Introduce omap_channel as a omap_dss_device parameter
Date: Thu, 02 Dec 2010 12:19:44 +0200 [thread overview]
Message-ID: <1291285184.778.17.camel@tubuntu> (raw)
In-Reply-To: <FCCFB4CDC6E5564B9182F639FC356087035F0A4A5C@dbde02.ent.ti.com>
On Thu, 2010-12-02 at 15:17 +0530, ext Taneja, Archit wrote:
> Hi,
> > If you can split this patch into the two parts I suggested
> > (if that's ok for you, you didn't comment on that one), and
> > check if there's anything to add to the commit descriptions,
> > I think we can go and apply this patch set.
>
> If I split this into 2 parts, the first patch will be just a line
> addition in display.h, I was beaten up by the community because of
> this in the previous version. One line patches in a series aren't
> taken very kindly :|. What I can do is clearly mention the 2 sets
> of things which this commit does, if you think that is good enough.
Ah, hmm... I thought this patch also changed dss_recheck_connections()
to use the new field, but now that I look at it, it doesn't. Why do you
add the new channel-member here, if it's not used? Shouldn't it be added
later, together with dss_recheck_connections()?
> > Btw, on what platforms have you tested this (or generally any
> > patches you send?). I only have 3430SDP currently that I can
> > easily use to test, so my testing is a bit limited.
> >
>
> This one I had tested throughly on 3430SDP, bootup on zoom2 and zoom3.
> I couldn't test on omap2, we have a n800 board but we don't know what panel
> driver we need to use, board-n8x0.c doesn't tell anything about. If you can
> tell me what panel driver to use etc I can try out.
Unfortunately the panel driver for N800 has not been ported to DSS2.
Tomi
next prev parent reply other threads:[~2010-12-02 10:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 7:22 [PATCH v5 0/7] OMAP: DSS2: Overlay Manager LCD2 support in DISPC Archit Taneja
2010-11-22 7:22 ` [PATCH v5 1/7] OMAP: DSS2: Add dss_features for omap4 and overlay manager related features Archit Taneja
2010-11-22 7:23 ` [PATCH v5 2/7] OMAP: DSS2: Represent DISPC register defines with channel as parameter Archit Taneja
2010-11-22 7:23 ` [PATCH v5 3/7] OMAP: DSS2: Introduce omap_channel as a omap_dss_device parameter Archit Taneja
2010-12-01 15:38 ` Tomi Valkeinen
2010-12-02 7:57 ` Taneja, Archit
2010-12-02 9:27 ` Tomi Valkeinen
2010-12-02 9:47 ` Taneja, Archit
2010-12-02 10:19 ` Tomi Valkeinen [this message]
2010-12-02 10:30 ` Taneja, Archit
2010-12-02 11:00 ` Tomi Valkeinen
2010-12-02 11:03 ` Taneja, Archit
2010-11-22 7:23 ` [PATCH v5 4/7] OMAP: DSS2: Change remaining Dispc functions for new 'channel' argument Archit Taneja
2010-11-22 7:23 ` [PATCH v5 5/7] OMAP: DSS2: LCD2 Channel Changes for DISPC Archit Taneja
2010-11-22 7:23 ` [PATCH v5 6/7] OMAP: DSS2: Use dss_features to handle DISPC bits removed on OMAP4 Archit Taneja
2010-11-22 7:23 ` [PATCH v5 7/7] OMAP: DSS2: Add new Overlay Manager Archit Taneja
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=1291285184.778.17.camel@tubuntu \
--to=tomi.valkeinen@nokia.com \
--cc=archit@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=mmittal@ti.com \
--cc=samreen@ti.com \
--cc=sumit.semwal@ti.com \
/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