From: Dmitry Osipenko <digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Sam Ravnborg <sam-uyr5N9Q2VtJg9hUCZPvPmw@public.gmane.org>,
Laurent Pinchart
<laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Frank Rowand
<frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v10 0/2] Silence missing-graph error for DRM bridges
Date: Wed, 1 Jul 2020 10:42:30 +0300 [thread overview]
Message-ID: <20200701074232.13632-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:
v10:- Corrected doc-comment, unbroke the of_graph_get_next_endpoint() and
improved commit's message in the "add of_graph_is_present()" patch.
Thanks to Laurent Pinchart for spotting the problems!
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 | 23 +++++++++++++++++++++++
include/linux/of_graph.h | 6 ++++++
3 files changed, 38 insertions(+)
--
2.26.0
WARNING: multiple messages have this Message-ID (diff)
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 v10 0/2] Silence missing-graph error for DRM bridges
Date: Wed, 1 Jul 2020 10:42:30 +0300 [thread overview]
Message-ID: <20200701074232.13632-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:
v10:- Corrected doc-comment, unbroke the of_graph_get_next_endpoint() and
improved commit's message in the "add of_graph_is_present()" patch.
Thanks to Laurent Pinchart for spotting the problems!
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 | 23 +++++++++++++++++++++++
include/linux/of_graph.h | 6 ++++++
3 files changed, 38 insertions(+)
--
2.26.0
WARNING: multiple messages have this Message-ID (diff)
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: linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: [PATCH v10 0/2] Silence missing-graph error for DRM bridges
Date: Wed, 1 Jul 2020 10:42:30 +0300 [thread overview]
Message-ID: <20200701074232.13632-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:
v10:- Corrected doc-comment, unbroke the of_graph_get_next_endpoint() and
improved commit's message in the "add of_graph_is_present()" patch.
Thanks to Laurent Pinchart for spotting the problems!
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 | 23 +++++++++++++++++++++++
include/linux/of_graph.h | 6 ++++++
3 files changed, 38 insertions(+)
--
2.26.0
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2020-07-01 7:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 7:42 Dmitry Osipenko [this message]
2020-07-01 7:42 ` [PATCH v10 0/2] Silence missing-graph error for DRM bridges Dmitry Osipenko
2020-07-01 7:42 ` Dmitry Osipenko
[not found] ` <20200701074232.13632-1-digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-07-01 7:42 ` [PATCH v10 1/2] of_graph: add of_graph_is_present() Dmitry Osipenko
2020-07-01 7:42 ` Dmitry Osipenko
2020-07-01 7:42 ` Dmitry Osipenko
[not found] ` <20200701074232.13632-2-digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-07-01 7:55 ` Laurent Pinchart
2020-07-01 7:55 ` Laurent Pinchart
2020-07-01 7:55 ` Laurent Pinchart
2020-07-01 7:42 ` [PATCH v10 2/2] drm/of: Make drm_of_find_panel_or_bridge() to check graph's presence Dmitry Osipenko
2020-07-01 7:42 ` Dmitry Osipenko
2020-07-01 7:42 ` Dmitry Osipenko
2020-07-01 9:02 ` [PATCH v10 0/2] Silence missing-graph error for DRM bridges Sam Ravnborg
2020-07-01 9:02 ` Sam Ravnborg
2020-07-01 9:02 ` Sam Ravnborg
[not found] ` <20200701090240.GA22218-uyr5N9Q2VtJg9hUCZPvPmw@public.gmane.org>
2020-07-01 9:31 ` Dmitry Osipenko
2020-07-01 9:31 ` Dmitry Osipenko
2020-07-01 9:31 ` 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=20200701074232.13632-1-digetx@gmail.com \
--to=digetx-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=sam-uyr5N9Q2VtJg9hUCZPvPmw@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 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.