public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: karl.beldan@gmail.com (Karl Beldan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: davinci: initial infrastructure for LCDC
Date: Wed, 5 Oct 2016 15:16:46 +0000	[thread overview]
Message-ID: <20161005151646.qpdycrefwbdrzhtq@gobelin> (raw)
In-Reply-To: <1475672732-17111-1-git-send-email-bgolaszewski@baylibre.com>

On Wed, Oct 05, 2016 at 03:05:30PM +0200, Bartosz Golaszewski wrote:
> After discussing the matter with Laurent Pinchart it turned out that
> using ti,tilcdc,panel was wrong and we should go with the new
> simple-vga-dac driver proposed by Maxime Ripard and currently being
> reviewed.
> 
> The da850-lcdk board on which I'm working has a THS8135 video DAC for
> which the new driver seems to be best suited and we'll be able to
> query the connected display for supported modes instead of hardcoding
> them in the dt as is needed for the panel driver.
> 

I meant to point to these new changes but then it slipped my mind, it is
clearly the way to go.

Regards, 
Karl


> In the meantime I'm posting two patches based on Karl Beldan's
> previous work that can already be merged.
> 
> The first one adds OF_DEV_AUXDATA entry to da8xx-dt.c. I changed the
> compatible string to the new one we're introducing in the tilcdc
> driver.
> 
> The second adds the lcd pins and the display node to da850.dtsi. As
> suggested by Sekhar: I moved the pins node, which was previously in
> da850-lcdk.dts, to da850.dtsi. I also squashed Karl's two patches and
> removed the panel node.
> 
> Tested on a da850-lcdk with an LCD display connected over VGA with
> two patches already posted to the drm mailing list:
> 
>   drm: tilcdc: add a da850-specific compatible string
>   drm: tilcdc: add a workaround for failed clk_set_rate()
> 
> and some additional work-in-progress/hacks on top of that.
> 
> Karl Beldan (2):
>   ARM: davinci: da8xx-dt: add OF_DEV_AUXDATA entry for lcdc
>   ARM: dts: da850: add a node for the LCD controller
> 
>  arch/arm/boot/dts/da850.dtsi     | 29 +++++++++++++++++++++++++++++
>  arch/arm/mach-davinci/da8xx-dt.c |  1 +
>  2 files changed, 30 insertions(+)
> 
> -- 
> 2.9.3
> 

      parent reply	other threads:[~2016-10-05 15:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05 13:05 [PATCH 0/2] ARM: davinci: initial infrastructure for LCDC Bartosz Golaszewski
2016-10-05 13:05 ` [PATCH 1/2] ARM: davinci: da8xx-dt: add OF_DEV_AUXDATA entry for lcdc Bartosz Golaszewski
2016-10-05 13:05 ` [PATCH 2/2] ARM: dts: da850: add a node for the LCD controller Bartosz Golaszewski
2016-10-15 17:42   ` Sekhar Nori
2016-10-15 19:40     ` Bartosz Golaszewski
2016-10-17  5:56     ` Tomi Valkeinen
2016-10-17  7:12       ` Sekhar Nori
2016-10-17  7:28         ` Bartosz Golaszewski
2016-10-17  7:33         ` Tomi Valkeinen
2016-10-17 11:40           ` Laurent Pinchart
2016-10-17 12:29             ` Tomi Valkeinen
2016-10-17 12:44               ` Laurent Pinchart
2016-10-17 14:01               ` Bartosz Golaszewski
2016-10-20 10:07                 ` Sekhar Nori
2016-10-20 10:21                   ` Tomi Valkeinen
2016-10-20 10:29                     ` Sekhar Nori
2016-10-05 15:16 ` Karl Beldan [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=20161005151646.qpdycrefwbdrzhtq@gobelin \
    --to=karl.beldan@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