linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: InKi Dae <daeinki@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] S5PV210: Add MIPI-DSI Driver.
Date: Sat, 03 Jul 2010 05:21:41 +0000	[thread overview]
Message-ID: <AANLkTilusz69vyqJE9v_8t3vDOeNex1wWC_u0m11kzjD@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinQ2jC1w6B9q-pirShQ9GJODDwmS6e80KWYRpMm@mail.gmail.com>

Hi, Jaya.

below is my answer.

2010/7/3 Jaya Kumar <jayakumar.lkml@gmail.com>:
> Hi InKi,
>
> 2010/7/2 InKi Dae <inki.dae@samsung.com>:
>> this patch addes MIPI-DSI Driver.
>>
>> to use this driver, some structures below should be added to machine
>> specific file.
>
> A quick question. I'm having difficulty understanding the larger
> picture here. There's the MIPI-DSI host controller driver (which I
> think is what this patch is) which is specific to this platform. Then
> there's the MIPI-DSI LCD panels which are supposed to be fully
> platform independent, right? and would thus ideally have a platform
> independent MIPI-DSI client driver?
>

hmm, is there any mipi-dsi master framework that it can use commonly
in linux kernel? my driver is dependent on platform a little because
lcd panel driver should include two header files.

> Would I be correct in saying this patch below does not provide such an
> abstraction and so structures that would be necessary for such a
> display driver (eg: struct mipi_lcd_driver ) appear to be declared in
> the samsung platform specific files. In other words, if we wanted to
> support a particular MIPI-DSI LCD panel, it would require a client
> driver that is tied intimately to this platform?
>
> Could you point us to an example mipi-dsi client driver that is using
> the patch you provided? ie: something that is calling
> s5p_dsim_register_lcd_driver. That would help us understand the
> abstraction that is being made here.

Ok, below is example code to mipi-dsi based lcd panel driver.

#include <plat/regs-dsim.h>
#include <plat/dsim.h>

static struct mipi_lcd_driver xxx_mipi_driver = {
           .name  = "xxx",
           .init  = xxx_init,
           .display_on = xxx_displsy_on,
           .set_link = xxx_set_link,
           .probe = xxx_probe,
           .suspend = xxx_suspend,
           .resume = xxx_resume,
};

static int xxx_init(void)
{
           s5p_dsim_register_lcd_driver(&xxx_mipi_driver);
           return 0;
}

static void xxx_exit(void)
{
          return;
}

module_init(xxx_init);
module_exit(xxx_exit);

at module_init, xxx_mipi_driver would be registered to mipi master
driver through
s5p_dsim_register_lcd_driver func and when master driver is probed, xxx_probe
would be called by probe func of master driver.

I wonder there is mipi-dsi master driver indenpendent on platform
fully in linux kernel.
if exsiting, I will use it as master driver. of course, the part
dependent on platform
would be implemented using that framework.

Thank you.

  reply	other threads:[~2010-07-03  5:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-29  8:31 [PATCH 0/3] ARM: S5PV210: Add MIPI-DSI support InKi Dae
     [not found] ` <4C29B1C1.2000209@samsung.com>
     [not found]   ` <4C29CABE.9020208@samsung.com>
2010-07-01 22:26     ` [PATCH 1/3] FB: Add some members for CPU Interface Andrew Morton
2010-07-02  8:47 ` [PATCH 0/2] ARM: S5PV210: Add MIPI-DSI support InKi Dae
2010-07-03  8:33   ` [PATCH v1 " InKi Dae
     [not found] ` <4C29B4BA.4090903@samsung.com>
2010-07-02  8:50   ` [PATCH 1/2] S5PV210: FB: Add MIPI-DSI and CPU Interface features InKi Dae
2010-07-03  8:35     ` [PATCH v1 " InKi Dae
     [not found] ` <4C29C766.7010901@samsung.com>
2010-07-02  8:51   ` [PATCH 2/2] S5PV210: Add MIPI-DSI Driver InKi Dae
2010-07-02 14:03     ` Ben Dooks
2010-07-02 18:08       ` InKi Dae
2010-07-03  1:44     ` Jaya Kumar
2010-07-03  5:21       ` InKi Dae [this message]
2010-07-03  7:20         ` InKi Dae
2010-07-03  8:42     ` [PATCH v1 " InKi Dae
2010-07-04 19:33       ` Guennadi Liakhovetski
2010-07-02 13:34 ` [PATCH 0/3] ARM: S5PV210: Add MIPI-DSI support Ben Dooks

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=AANLkTilusz69vyqJE9v_8t3vDOeNex1wWC_u0m11kzjD@mail.gmail.com \
    --to=daeinki@gmail.com \
    --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).