u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Anatolij Gustschin <agust@denx.de>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot <u-boot@lists.denx.de>
Subject: Please pull u-boot-video
Date: Fri, 7 Apr 2023 21:51:26 +0200	[thread overview]
Message-ID: <20230407215126.2d01ae57@crub> (raw)

Hi Tom,

please pull video updates for v2023.07.

CI: https://source.denx.de/u-boot/custodians/u-boot-video/-/pipelines/15944

Thanks,
Anatolij

The following changes since commit 340bebf9c799793affefd166875d5776744988bd:

  Merge branch '2023-04-06-assorted-updates' (2023-04-07 10:44:19 -0400)

are available in the Git repository at:

  https://source.denx.de/u-boot/custodians/u-boot-video.git tags/video-20230407

for you to fetch changes up to cc54a924cd28a2d1b0f0035bd7d78532b6bc4ad8:

  simple_panel: support simple MIPI DSI panels (2023-04-07 19:54:31 +0200)

----------------------------------------------------------------
 - fix building sandbox without SDL
 - improve tegra DC driver to work with panel ops and implement
   native 180 degree panel rotation support
 - add T30 support to tegra DC driver
 - add DSI driver (based on mainline Linux one with minor
   adjustments, only T30 tested)
 - add get_display_timing ops to simple panel driver
 - extend simple panel driver to use it for MIPI DSI panels
   which do not require additional DSI commands for setup

----------------------------------------------------------------
Marcel Ziswiler (1):
      tegra: lcd: video: integrate display driver for t30

Simon Glass (1):
      sandbox: video: Fix building without SDL

Svyatoslav Ryhel (10):
      video: move tegra dc driver into own folder
      video: tegra-dc: get clocks from device tree
      video: tegra-dc: request timings from panel driver first
      video: tegra-dc: assign regmap directly
      video: tegra-dc: add 180 degree panel rotation
      video: tegra-dc: add panel_set_backlight call
      video: tegra-dc: pass DC regmap to internal devices
      video: tegra20: add DSI controller driver
      simple_panel: add support for get_display_timing
      simple_panel: support simple MIPI DSI panels

 arch/arm/dts/tegra30-u-boot.dtsi              |   9 +
 arch/arm/include/asm/arch-tegra/dc.h          |   8 +
 arch/arm/include/asm/arch-tegra30/display.h   |  28 +
 arch/arm/include/asm/arch-tegra30/dsi.h       | 217 +++++++
 arch/arm/include/asm/arch-tegra30/pwm.h       |  13 +
 arch/sandbox/include/asm/test.h               |   8 +
 drivers/video/Kconfig                         |  11 +-
 drivers/video/Makefile                        |   2 +-
 drivers/video/simple_panel.c                  |  47 +-
 drivers/video/tegra20/Kconfig                 |  17 +
 drivers/video/tegra20/Makefile                |   4 +
 drivers/video/tegra20/mipi-phy.c              | 134 ++++
 drivers/video/tegra20/mipi-phy.h              |  48 ++
 drivers/video/{tegra.c => tegra20/tegra-dc.c} | 123 ++--
 drivers/video/tegra20/tegra-dsi.c             | 864 ++++++++++++++++++++++++++
 15 files changed, 1484 insertions(+), 49 deletions(-)
 create mode 100644 arch/arm/include/asm/arch-tegra30/display.h
 create mode 100644 arch/arm/include/asm/arch-tegra30/dsi.h
 create mode 100644 arch/arm/include/asm/arch-tegra30/pwm.h
 create mode 100644 drivers/video/tegra20/Kconfig
 create mode 100644 drivers/video/tegra20/Makefile
 create mode 100644 drivers/video/tegra20/mipi-phy.c
 create mode 100644 drivers/video/tegra20/mipi-phy.h
 rename drivers/video/{tegra.c => tegra20/tegra-dc.c} (82%)
 create mode 100644 drivers/video/tegra20/tegra-dsi.c

             reply	other threads:[~2023-04-07 19:51 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07 19:51 Anatolij Gustschin [this message]
2023-04-08 18:18 ` Please pull u-boot-video Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2023-10-23 10:17 Anatolij Gustschin
2023-10-23 16:58 ` Tom Rini
2023-08-14  6:02 Anatolij Gustschin
2023-08-14 15:04 ` Tom Rini
2023-08-01 12:52 Anatolij Gustschin
2023-08-01 15:57 ` Tom Rini
2023-07-16 20:04 Anatolij Gustschin
2023-07-17 14:38 ` Tom Rini
2023-05-05  8:25 Anatolij Gustschin
2023-05-05 17:14 ` Tom Rini
2023-02-04 19:09 Anatolij Gustschin
2023-02-06 14:55 ` Tom Rini
2022-10-30 21:16 Anatolij Gustschin
2022-10-31 12:52 ` Tom Rini
2022-06-25  7:34 Anatolij Gustschin
2022-06-25 15:57 ` Tom Rini
2022-03-14 22:33 Anatolij Gustschin
2022-03-15 12:13 ` Tom Rini
2022-03-19 17:05   ` Anatolij Gustschin
2022-03-19 17:44     ` Tom Rini
2022-03-19 17:55       ` Anatolij Gustschin
2021-12-28 14:25 Anatolij Gustschin
2021-12-28 16:26 ` Tom Rini
2021-10-09 21:29 Anatolij Gustschin
2021-10-10 20:04 ` Tom Rini
2021-08-05 22:01 Anatolij Gustschin
2021-08-06 21:22 ` Tom Rini
2021-06-05 13:00 Anatolij Gustschin
2021-06-07 11:21 ` Tom Rini
2021-04-24 14:33 Anatolij Gustschin
2021-04-24 21:42 ` Tom Rini
2021-04-10 21:21 Anatolij Gustschin
2021-04-11 18:10 ` Tom Rini
2021-03-19  8:02 Anatolij Gustschin
2021-03-19 12:21 ` Tom Rini
2021-02-22 12:17 Anatolij Gustschin
2021-02-22 17:32 ` Tom Rini
2020-10-26 20:43 Anatolij Gustschin
2020-10-27 14:50 ` Tom Rini
2020-10-27 19:37   ` Anatolij Gustschin
2020-10-27 19:43     ` Tom Rini
2020-10-27 19:47       ` Anatolij Gustschin
2020-10-18 20:36 Anatolij Gustschin
2020-10-19 21:17 ` Tom Rini
2020-08-04  7:42 Anatolij Gustschin
2020-08-04 20:55 ` Tom Rini
2020-06-29 19:50 Anatolij Gustschin
2020-06-29 19:58 ` Tom Rini
2020-06-28 12:27 Anatolij Gustschin
2020-06-29  1:30 ` Tom Rini
2020-06-18 21:12 Anatolij Gustschin
2020-06-19 13:24 ` Tom Rini
2020-04-27  8:32 Anatolij Gustschin
2020-04-27 16:20 ` Tom Rini
2020-04-02 16:13 Anatolij Gustschin
2020-04-02 16:18 ` Anatolij Gustschin
2020-04-05 23:04 ` Tom Rini
2020-02-10 17:07 Anatolij Gustschin
2020-02-10 19:16 ` Tom Rini
2020-01-18 16:19 Anatolij Gustschin
2020-01-18 16:28 ` Tom Rini
     [not found] <20200102205451.4123cbe9@crub>
2020-01-03 14:46 ` Tom Rini
2019-12-10 20:38 Anatolij Gustschin
2019-12-11 13:15 ` Tom Rini

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=20230407215126.2d01ae57@crub \
    --to=agust@denx.de \
    --cc=trini@konsulko.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 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).