From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/5] rockchip: video: rk_hdmi: migrate to livetree
Date: Fri, 23 Feb 2018 19:26:38 +0100 [thread overview]
Message-ID: <20180223192638.4e142fb2@crub> (raw)
In-Reply-To: <1519403933-64408-4-git-send-email-philipp.tomsich@theobroma-systems.com>
On Fri, 23 Feb 2018 17:38:51 +0100
Philipp Tomsich philipp.tomsich at theobroma-systems.com wrote:
> The rk_hdmi (shared functions for multiple HDMI mini-drivers) has been
> using devfdt_get_addr() to read the HDMI controller's IO base address.
> This will cause a failure with a live tree.
>
> This changes the driver to use dev_read_addr() which is safe both for
> flat trees and live trees.
>
> Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
> Tested-by: Klaus Goger <klaus.goger@theobroma-systems.com>
Reviewed-by: Anatolij Gustschin <agust@denx.de>
next prev parent reply other threads:[~2018-02-23 18:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 16:38 [U-Boot] [PATCH 0/5] rockchip: video: migrate RK3399 w/ HDMI to livetree Philipp Tomsich
2018-02-23 16:38 ` [U-Boot] [PATCH 1/5] core: ofnode: add ofnode_get_parent function Philipp Tomsich
2018-02-23 18:22 ` Anatolij Gustschin
2018-02-23 20:58 ` Simon Glass
2018-02-23 16:38 ` [U-Boot] [PATCH 2/5] core: add ofnode_get_by_phandle() api Philipp Tomsich
2018-02-23 16:38 ` [U-Boot] [PATCH 3/5] rockchip: video: rk_hdmi: migrate to livetree Philipp Tomsich
2018-02-23 18:26 ` Anatolij Gustschin [this message]
2018-02-23 16:38 ` [U-Boot] [PATCH 4/5] rockchip: video: rk_vop: " Philipp Tomsich
2018-02-23 19:40 ` Anatolij Gustschin
2018-02-23 16:38 ` [U-Boot] [PATCH 5/5] rockchip: video: update MAINTAINERS Philipp Tomsich
2018-02-23 19:43 ` Anatolij Gustschin
2018-02-23 16:48 ` [U-Boot] [PATCH 0/5] rockchip: video: migrate RK3399 w/ HDMI to livetree Dr. Philipp Tomsich
2018-02-23 20:10 ` Anatolij Gustschin
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=20180223192638.4e142fb2@crub \
--to=agust@denx.de \
--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.