linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Archit Taneja <archit@ti.com>
Cc: linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 0/9] OMAPDSS: minor fixes & cleanups
Date: Mon, 22 Oct 2012 06:54:35 +0000	[thread overview]
Message-ID: <5084EDAB.4070402@ti.com> (raw)
In-Reply-To: <5084DE3D.1050502@ti.com>

[-- Attachment #1: Type: text/plain, Size: 1443 bytes --]

On 2012-10-22 08:48, Archit Taneja wrote:
> On Wednesday 17 October 2012 04:50 PM, Tomi Valkeinen wrote:
>> Hi,
>>
>> This series contains minor cleanups and fixes for omapdss.
> 
> This series looks fine to me. I have a related cleanup patch which you
> may consider adding to the series.
> 
> Thanks,
> Archit
> 
> From: Archit Taneja <archit@ti.com>
> Date: Thu, 18 Oct 2012 16:51:57 +0530
> Subject: [PATCH] OMAPDSS: Remove acb and acbi fields from omap_dss_device
> 
> acbi and acb fields were meant for passive matrix panels which omapdss
> doesn't
> support any longer. Remove these fields from omap_dss_device struct.
> 
> Signed-off-by: Archit Taneja <archit@ti.com>
> ---
>  include/video/omapdss.h |    4 ----
>  1 file changed, 4 deletions(-)
> 
> diff --git a/include/video/omapdss.h b/include/video/omapdss.h
> index 88c8294..f39e6aa 100644
> --- a/include/video/omapdss.h
> +++ b/include/video/omapdss.h
> @@ -621,10 +621,6 @@ struct omap_dss_device {
>      struct {
>          struct omap_video_timings timings;
> 
> -        int acbi;    /* ac-bias pin transitions per interrupt */
> -        /* Unit: line clocks */
> -        int acb;    /* ac-bias pin frequency */
> -
>          enum omap_dss_dsi_pixel_format dsi_pix_fmt;
>          enum omap_dss_dsi_mode dsi_mode;
>          struct omap_dss_dsi_videomode_timings dsi_vm_timings;

Thanks, applied to omapdss tree.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 897 bytes --]

      reply	other threads:[~2012-10-22  6:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-17 11:20 [PATCH 0/9] OMAPDSS: minor fixes & cleanups Tomi Valkeinen
2012-10-17 11:20 ` [PATCH 1/9] OMAPDSS: DSI: fix dsi_get_dsidev_from_id() Tomi Valkeinen
2012-10-17 11:20 ` [PATCH 2/9] OMAPDSS: fix registering the vsync isr in apply Tomi Valkeinen
2012-10-17 11:20 ` [PATCH 3/9] OMAPDSS: DISPC: constify function parameters Tomi Valkeinen
2012-10-17 11:20 ` [PATCH 4/9] OMAPDSS: combine LCD related config into one func Tomi Valkeinen
2012-10-17 11:20 ` [PATCH 5/9] OMAPDSS: remove declarations for non-existing funcs Tomi Valkeinen
2012-10-17 11:20 ` [PATCH 6/9] OMAPDSS: DISPC: remove struct omap_overlay use Tomi Valkeinen
2012-10-17 11:20 ` [PATCH 7/9] OMAPDSS: DISPC: cleanup lcd and digit enable Tomi Valkeinen
2012-10-17 11:20 ` [PATCH 8/9] OMAPDSS: DISPC: add dispc_mgr_get_sync_lost_irq() Tomi Valkeinen
2012-10-17 11:20 ` [PATCH 9/9] OMAPDSS: DISPC: cleanup lcd/digit enable/disable Tomi Valkeinen
2012-10-17 14:50   ` Archit Taneja
2012-10-18 10:09     ` Tomi Valkeinen
2012-10-22  5:48 ` [PATCH 0/9] OMAPDSS: minor fixes & cleanups Archit Taneja
2012-10-22  6:54   ` Tomi Valkeinen [this message]

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=5084EDAB.4070402@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=archit@ti.com \
    --cc=linux-fbdev@vger.kernel.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).