From: Archit Taneja <a0393947@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 0/6] OMAPDSS: Misc fixes and cleanups
Date: Tue, 08 May 2012 12:24:04 +0000 [thread overview]
Message-ID: <4FA90D94.3020705@ti.com> (raw)
In-Reply-To: <1336478337.5761.29.camel@deskari>
On Tuesday 08 May 2012 05:28 PM, Tomi Valkeinen wrote:
> On Mon, 2012-05-07 at 16:51 +0530, Archit Taneja wrote:
>> The first patch in this series is a follow up on the previously posted series
>> 'OMAPDSS: APPLY: Treat overlay manager timings as shadow registers'. It is
>> required for HDMI and DPI interfaces to work properly, it ensures manager
>> timings are applied in the set_timing() ops for these interfaces.
>>
>> The next 3 patches remove some unnecessary usage of omap_dss_device pointer in
>> DISPC and APPLY.
>>
>> The last 2 patches are miscellaneous fixes and are self explanatory.
>>
>> Reference tree containing this series:
>>
>> git://gitorious.org/~boddob/linux-omap-dss2/archit-dss2-clone.git mgr_timing_and_fixes
>>
>> Tested on OMAP4 SDP.
>>
>> Archit Taneja (6):
>> OMAPDSS: DPI/HDMI: Apply manager timings even if panel is disabled
>> OMAPDSS: APPLY: Remove an unnecessary omap_dss_device pointer
>> OMAPDSS: DISPC: Remove omap_dss_device pointer usage from
>> dispc_mgr_pclk_rate()
>> OMAPDSS: DISPC: Remove usage of dispc_mgr_get_device()
>> OMAPDSS: Fix DSI_FCLK clock source selection
>> OMAPDSS: DISPC: Remove Fake VSYNC support
>
> The first four patches seem to be related (or at least based) to the
> set_timings series (and the first patch you already had included in
> later version).
>
> Should I take the two last patches and apply them already, as they are
> fine and don't depend on anything? You could add the first 4 patches
> into the set_timings series.
Yes, you can apply the last 2 patches.
Thanks,
Archit
>
> Tomi
>
WARNING: multiple messages have this Message-ID (diff)
From: Archit Taneja <a0393947@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 0/6] OMAPDSS: Misc fixes and cleanups
Date: Tue, 8 May 2012 17:42:04 +0530 [thread overview]
Message-ID: <4FA90D94.3020705@ti.com> (raw)
In-Reply-To: <1336478337.5761.29.camel@deskari>
On Tuesday 08 May 2012 05:28 PM, Tomi Valkeinen wrote:
> On Mon, 2012-05-07 at 16:51 +0530, Archit Taneja wrote:
>> The first patch in this series is a follow up on the previously posted series
>> 'OMAPDSS: APPLY: Treat overlay manager timings as shadow registers'. It is
>> required for HDMI and DPI interfaces to work properly, it ensures manager
>> timings are applied in the set_timing() ops for these interfaces.
>>
>> The next 3 patches remove some unnecessary usage of omap_dss_device pointer in
>> DISPC and APPLY.
>>
>> The last 2 patches are miscellaneous fixes and are self explanatory.
>>
>> Reference tree containing this series:
>>
>> git://gitorious.org/~boddob/linux-omap-dss2/archit-dss2-clone.git mgr_timing_and_fixes
>>
>> Tested on OMAP4 SDP.
>>
>> Archit Taneja (6):
>> OMAPDSS: DPI/HDMI: Apply manager timings even if panel is disabled
>> OMAPDSS: APPLY: Remove an unnecessary omap_dss_device pointer
>> OMAPDSS: DISPC: Remove omap_dss_device pointer usage from
>> dispc_mgr_pclk_rate()
>> OMAPDSS: DISPC: Remove usage of dispc_mgr_get_device()
>> OMAPDSS: Fix DSI_FCLK clock source selection
>> OMAPDSS: DISPC: Remove Fake VSYNC support
>
> The first four patches seem to be related (or at least based) to the
> set_timings series (and the first patch you already had included in
> later version).
>
> Should I take the two last patches and apply them already, as they are
> fine and don't depend on anything? You could add the first 4 patches
> into the set_timings series.
Yes, you can apply the last 2 patches.
Thanks,
Archit
>
> Tomi
>
next prev parent reply other threads:[~2012-05-08 12:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 11:21 [PATCH 0/6] OMAPDSS: Misc fixes and cleanups Archit Taneja
2012-05-07 11:33 ` Archit Taneja
2012-05-07 11:21 ` [PATCH 1/6] OMAPDSS: DPI/HDMI: Apply manager timings even if panel is disabled Archit Taneja
2012-05-07 11:33 ` Archit Taneja
2012-05-07 11:21 ` [PATCH 2/6] OMAPDSS: APPLY: Remove an unnecessary omap_dss_device pointer Archit Taneja
2012-05-07 11:33 ` Archit Taneja
2012-05-07 11:21 ` [PATCH 3/6] OMAPDSS: DISPC: Remove omap_dss_device pointer usage from dispc_mgr_pclk_rate() Archit Taneja
2012-05-07 11:33 ` Archit Taneja
2012-05-07 11:21 ` [PATCH 4/6] OMAPDSS: DISPC: Remove usage of dispc_mgr_get_device() Archit Taneja
2012-05-07 11:33 ` Archit Taneja
2012-05-07 11:21 ` [PATCH 5/6] OMAPDSS: Fix DSI_FCLK clock source selection Archit Taneja
2012-05-07 11:33 ` Archit Taneja
2012-05-07 11:21 ` [PATCH 6/6] OMAPDSS: DISPC: Remove Fake VSYNC support Archit Taneja
2012-05-07 11:33 ` Archit Taneja
2012-05-08 11:58 ` [PATCH 0/6] OMAPDSS: Misc fixes and cleanups Tomi Valkeinen
2012-05-08 11:58 ` Tomi Valkeinen
2012-05-08 12:12 ` Archit Taneja [this message]
2012-05-08 12:24 ` Archit Taneja
2012-05-08 23:38 ` Russ Dill
2012-05-08 23:38 ` Russ Dill
2012-05-09 5:24 ` Archit Taneja
2012-05-09 5:36 ` 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=4FA90D94.3020705@ti.com \
--to=a0393947@ti.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.