linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 06/57] fbdev: sh_mobile_hdmi: Don't access LCDC channel
Date: Tue, 13 Dec 2011 23:02:11 +0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1112132354410.20293@axis700.grange> (raw)
In-Reply-To: <1323784972-24205-7-git-send-email-laurent.pinchart@ideasonboard.com>

On Tue, 13 Dec 2011, Laurent Pinchart wrote:

> Instead of relying on info->par being a pointer to an LCDC channel, cast
> the notifier block pointer to an sh_hdmi pointer.
> 
> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
>  drivers/video/sh_mobile_hdmi.c |    6 +++---
>  1 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/video/sh_mobile_hdmi.c b/drivers/video/sh_mobile_hdmi.c
> index 647ba98..b1e90f5 100644
> --- a/drivers/video/sh_mobile_hdmi.c
> +++ b/drivers/video/sh_mobile_hdmi.c
> @@ -225,6 +225,8 @@ struct sh_hdmi {
>  	struct notifier_block notifier;
>  };
>  
> +#define notifier_to_hdmi(n)	container_of(n, struct sh_hdmi, notifier)
> +
>  static void hdmi_write(struct sh_hdmi *hdmi, u8 data, u8 reg)
>  {
>  	iowrite8(data, hdmi->base + reg);
> @@ -1204,9 +1206,7 @@ static int sh_hdmi_notify(struct notifier_block *nb,
>  {
>  	struct fb_event *event = data;
>  	struct fb_info *info = event->info;
> -	struct sh_mobile_lcdc_chan *ch = info->par;
> -	struct sh_mobile_lcdc_board_cfg	*board_cfg = &ch->cfg.board_cfg;
> -	struct sh_hdmi *hdmi = board_cfg->board_data;
> +	struct sh_hdmi *hdmi = notifier_to_hdmi(nb);
>  
>  	if (!hdmi || nb != &hdmi->notifier || hdmi->info != info)

Then you also can drop the first two of the three checks above. If I'm not 
mistaken, in a HDMI / LCD set up, if this notifier is called for the LCD 
panel, hdmi will wtill point to the HDMI-related sh_hdmi object, whose 
->info will then mismatch the info pointer, derived from the notifier 
"data" pointer.

>  		return NOTIFY_DONE;
> -- 
> 1.7.3.4

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/

  reply	other threads:[~2011-12-13 23:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13 14:02 [PATCH 06/57] fbdev: sh_mobile_hdmi: Don't access LCDC channel in notifier callback Laurent Pinchart
2011-12-13 23:02 ` Guennadi Liakhovetski [this message]
2011-12-14 10:41 ` Laurent Pinchart
2011-12-14 10:47 ` Laurent Pinchart

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=Pine.LNX.4.64.1112132354410.20293@axis700.grange \
    --to=g.liakhovetski@gmx.de \
    --cc=linux-fbdev@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).