From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>
Cc: dri-devel@lists.freedesktop.org, linux-tegra@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v9 0/2] Silence missing-graph error for DRM bridges
Date: Wed, 1 Jul 2020 05:16:15 +0300 [thread overview]
Message-ID: <20200701021617.12030-1-digetx@gmail.com> (raw)
Hi!
This small series improves DRM bridges code by silencing a noisy error
coming from of-graph code for the device-trees that are missing a
display bridge graph.
graph: no port node found in ...
One example where this error happens is an older bridge-less DTB used
in conjunction with a newer kernel which has a display controller driver
that supports DRM bridges.
Changelog:
v9: - These two patches are factored out from [1] in order to ease applying
of the patches.
- The of_graph_presents() is renamed to of_graph_is_present() like it
was requested by Rob Herring in the review comment to [1].
- Added Rob's r-b.
[1] https://patchwork.ozlabs.org/project/linux-tegra/list/?series=184102
Dmitry Osipenko (2):
of_graph: add of_graph_is_present()
drm/of: Make drm_of_find_panel_or_bridge() to check graph's presence
drivers/gpu/drm/drm_of.c | 9 +++++++
drivers/of/property.c | 52 +++++++++++++++++++++++++++++++++-------
include/linux/of_graph.h | 6 +++++
3 files changed, 58 insertions(+), 9 deletions(-)
--
2.26.0
next reply other threads:[~2020-07-01 2:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 2:16 Dmitry Osipenko [this message]
2020-07-01 2:16 ` [PATCH v9 1/2] of_graph: add of_graph_is_present() Dmitry Osipenko
2020-07-01 5:45 ` Laurent Pinchart
2020-07-01 6:42 ` Dmitry Osipenko
2020-07-01 2:16 ` [PATCH v9 2/2] drm/of: Make drm_of_find_panel_or_bridge() to check graph's presence Dmitry Osipenko
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=20200701021617.12030-1-digetx@gmail.com \
--to=digetx@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=frowand.list@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.com \
/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).