All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kamps, John-Eric <John-Eric.Kamps@Honeywell.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] sun50i: Allwinner A64: Add LVDS video support - question about how to proceed
Date: Wed, 24 Apr 2019 07:01:14 +0000	[thread overview]
Message-ID: <SN6PR07MB519931E87BFABF2E7947100FAB3C0@SN6PR07MB5199.namprd07.prod.outlook.com> (raw)

Hi all. 
I'm new in working with the community and where I can ask question about how something should be done. 

I need LVDS on the Allwinner A64 and checked the source code. 
There is the code for sunxi (A20 and so on) with the file "sunxi_display.c" 
and the new one for my sun50i (A64) "sunxi_de2.c". 
both are sharing files between each other but for sun50i the sunxi_display.c is disabled from kconfig for my chip. 

I see 2 ways to enable LVDS on sun50i, but I don't know in which direction the development should go. I can enable in KCONFIG that the sunxi_display could be also build for A64, but I think it has a reason why this is disabled and only the sunxi_de2 system should be used, or?

So going the way that there was a patch to enable the LCD over the sunxi_de2 file (git: 1d7eef3f3fbd82796a4ced3adda0a9041393141d). I can add the needed pinmux settings in the corresponding files and enable in kconfig that there is also the menu to setup CONFIG_VIDEO_LCD_IF_LVDS and CONFIG_VIDEO_LCD_IF_PARALLEL like for CONFIG_VIDEO_SUNXI. Also with the other settings there.

Is these the correct way to add them?

If yes how the backlight will be used and added? Because the sunxi_display.c has it integrated with getting the extra settings from menuconfig. Is it needed to add the same settings as well to sunxi_lcd.c like in sunxi_display.c? Or is there a different system to enable backlight in the future from the information of the dts-files? If yes did someone can give me a hint where I can find something about it?

Thanks a lot
Kind regards
John-Eric Kamps

                 reply	other threads:[~2019-04-24  7:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=SN6PR07MB519931E87BFABF2E7947100FAB3C0@SN6PR07MB5199.namprd07.prod.outlook.com \
    --to=john-eric.kamps@honeywell.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.