linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Dooks <ben@simtec.co.uk>
To: InKi Dae <daeinki@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	linux-fbdev-devel@lists.sourceforge.net,
	Kyungmin Park <kmpark@infradead.org>
Subject: Re: Samsung SoC Framebuffer Driver issue.
Date: Mon, 08 Jun 2009 23:36:50 +0100	[thread overview]
Message-ID: <4A2D9282.6080609@simtec.co.uk> (raw)
In-Reply-To: <90b950fc0906072153j6308059eq4d6f864c97a2003d@mail.gmail.com>

InKi Dae wrote:
> Hello,  Ben  Dooks.
> 
> I am trying to develop Samsung SoC Framebuffer Driver for S5PC100 but
> I faced some problems about design. so I have some questions about those.
> 
> there are some differences between LCD Controller registers of S3C64XX
> and S5PC100 like the following.
> 
> . regiters not used by S3C64XX were added to S5PC100 also BPP MODE.
> . WindowX Palette Data Index registers were removed from lcd
> controller of S3C64XX and Palette Memory Registers were added to one
> of S5PC100
> 
> 
> 1.
> Your framebuffer driver, drivers/video/s3c-fb.c, is related to only S3C64XX.
> and I'd like to divide framebuffer driver into common logical driver
> for supporting S3C64XX and S5PC100 and S5PC100 specific driver.
> but your driver needs to modifying because calling register control
> commands in s3c-fb.c directly.

Actually, it should also support the s3c2443 driver. You might find some
interesting answers to the further questions by looking at how that works
via the architecture specific includes.

> How do you think about that ?
> 
> 2.
> S3C64XX LCD Controller's registers are similar with S5PC100's, so I
> wouldn't modify register prefix.
> but some registers should added to definition file
> (arch/arm/mach-s3c6400/include/mach/regs-fb.h).

I don't have documentation for any of these newer chips, so cannot make
much of a comment without any more detailed data.

> which way do you prefer adding some registers to
> arch/arm/mach-s3c6400/include/mach/regs-fb.h or creating new
> definition file for S5PC100 ?
> 
> If you give me your comments for the issues above, I will modify
> Samsung SoC Framebuffer Driver to be supported for S3C64XX and
> S5PC100.
> In the result, I expect that your driver will be divided into logical
> driver and specific driver supporting S3C64XX and S5PC100 or either
> S3C64XX or S5PC100.
> If the driver would be completed, logical driver, s3c-fb.c, would
> support S3C64XX, S5PC100 and also S5PC110.

I'll let you have a think about this wrt to the answer supplied for #1,
and see if you need any further information about it after that.

> Please give me your comments and advices.
> 
> Best Regards,
> InKi Dae.


-- 
Ben Dooks, Software Engineer, Simtec Electronics

http://www.simtec.co.uk/

  reply	other threads:[~2009-06-08 22:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08  4:53 Samsung SoC Framebuffer Driver issue InKi Dae
2009-06-08 22:36 ` Ben Dooks [this message]
2009-06-09  2:33   ` InKi Dae

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=4A2D9282.6080609@simtec.co.uk \
    --to=ben@simtec.co.uk \
    --cc=daeinki@gmail.com \
    --cc=kmpark@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@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).