linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] video: Add i.MX23/28 framebuffer driver
Date: Fri, 18 Feb 2011 08:30:55 +0000	[thread overview]
Message-ID: <20110218083055.GE24426@pengutronix.de> (raw)
In-Reply-To: <20110218052418.GA18053@S2100-06.ap.freescale.net>

On Fri, Feb 18, 2011 at 01:24:20PM +0800, Shawn Guo wrote:
> Sorry, I did not catch up with v1 of the patch set.
> 
> I have a overall comment on the driver.  There is many occurrences
> of mx23, mx28 etc. throughout the file.  IMHO, this is not a good
> idea.  It may be better to use the IP version to handle the
> differences.  In this way, if we have another SoC coming later
> using the same LCDIF revision as i.MX28.  The driver could
> immediately fit in without code change, ideally.
> 
> The only problem with version register is that the offset of LCDIF
> version register is different on i.MX28 from i.MX23.

Can opener inside can. I love it ;)

> You still need
> cpu_is_mx23 to read the correct version.
> 
> BTW, I would try to use cpu_is_mx23 than cpu_is_mx28, as the 'else'
> of cpu_is_mx23 could _possibly_ cover later SoC as well as i.MX28.

There is only one cpu_is_mx28 in the driver without else. I can switch
MXSFB_MX23 and MXSFB_MX28 to MXSFB_V3 and MXSFB_V4 if you like it
better.

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2011-02-18  8:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1297850199-1688-1-git-send-email-s.hauer@pengutronix.de>
2011-02-16  9:56 ` [PATCH 1/2] video: Add i.MX23/28 framebuffer driver Sascha Hauer
2011-02-18  5:24   ` Shawn Guo
2011-02-18  8:30     ` Sascha Hauer [this message]
2011-02-18  8:57       ` Shawn Guo
2011-02-18 12:29   ` Shawn Guo
2011-02-21 14:17     ` Sascha Hauer
     [not found] <1298880152-28913-1-git-send-email-s.hauer@pengutronix.de>
2011-02-28  8:02 ` Sascha Hauer
     [not found] <1297257651-8002-1-git-send-email-s.hauer@pengutronix.de>
2011-02-09 13:20 ` Sascha Hauer
2011-02-09 13:35   ` Lothar Waßmann
2011-02-10  3:16   ` Li Frank-B20596
2011-02-10  8:51     ` Juergen Beisert
2011-02-10  9:15       ` Li Frank-B20596
2011-02-10  9:52         ` Juergen Beisert
2011-02-10 10:37           ` Li Frank-B20596
2011-02-10 11:12             ` Juergen Beisert
2011-02-10 12:23               ` Li Frank-B20596
2011-02-10  9:23   ` Li Frank-B20596
2011-02-10  9:46     ` Juergen Beisert
2011-02-10 10:08       ` Li Frank-B20596
2011-02-10 10:47       ` Wolfram Sang
2011-02-10 11:51         ` Sascha Hauer
2011-02-10 12:32           ` Li Frank-B20596

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=20110218083055.GE24426@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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).