From: Imre Deak <imre.deak@intel.com>
To: Neil Armstrong <narmstrong@baylibre.com>,
Boris Brezillon <boris.brezillon@collabora.com>
Cc: dri-devel@lists.freedesktop.org,
Mark Rutland <mark.rutland@arm.com>,
Nikita Yushchenko <nikita.yoush@cogentembedded.com>,
devicetree@vger.kernel.org,
Andrey Smirnov <andrew.smirnov@gmail.com>,
Jonas Karlman <jonas@kwiboo.se>,
Seung-Woo Kim <sw0312.kim@samsung.com>,
Jernej Skrabec <jernej.skrabec@siol.net>,
Rob Herring <robh+dt@kernel.org>,
Kyungmin Park <kyungmin.park@samsung.com>,
Boris Brezillon <boris.brezillon@collabora.com>,
Thierry Reding <thierry.reding@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
kernel@collabora.com, Sam Ravnborg <sam@ravnborg.org>,
Chris Healy <cphealy@gmail.com>
Subject: Re: [PATCH v6 1/4] drm/bridge: Add a drm_bridge_state object
Date: Tue, 7 Jan 2020 16:46:05 +0200 [thread overview]
Message-ID: <20200107144605.GD29830@ideak-desk.fi.intel.com> (raw)
In-Reply-To: <20200106143409.32321-2-narmstrong@baylibre.com>
Hi,
On Mon, Jan 06, 2020 at 03:34:06PM +0100, Neil Armstrong wrote:
> From: Boris Brezillon <boris.brezillon@collabora.com>
>
> One of the last remaining objects to not have its atomic state.
>
> This is being motivated by our attempt to support runtime bus-format
> negotiation between elements of the bridge chain.
> This patch just paves the road for such a feature by adding a new
> drm_bridge_state object inheriting from drm_private_obj so we can
> re-use some of the existing state initialization/tracking logic.
>
> Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>
> Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
> ---
> [...]
> +
> +/**
> + * __drm_atomic_helper_bridge_duplicate_state() - Copy atomic bridge state
> + * @bridge: bridge object
> + * @state: atomic bridge state
> + *
> + * Copies atomic state from a bridge's current state and resets inferred values.
> + * This is useful for drivers that subclass the bridge state.
> + */
> +void __drm_atomic_helper_bridge_duplicate_state(struct drm_bridge *bridge,
> + struct drm_bridge_state *state)
> +{
> + __drm_atomic_helper_private_obj_duplicate_state(&bridge->base,
> + &state->base);
When DRM and DRM_KMS_HELPER are built as modules the above will cause the
following build error:
depmod: ERROR: Cycle detected: drm_kms_helper -> drm -> drm_kms_helper
depmod: ERROR: Found 2 modules in dependency cycles!
Using __drm_atomic_helper_private_obj_duplicate_state will add the
drm.ko->drm_kms_helper.ko dependency but drm_kms_helper.ko already
depends on drm.ko
--Imre
next prev parent reply other threads:[~2020-01-07 14:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 14:34 [PATCH v6 0/4] drm: Add support for bus-format negotiation Neil Armstrong
2020-01-06 14:34 ` [PATCH v6 1/4] drm/bridge: Add a drm_bridge_state object Neil Armstrong
2020-01-07 14:46 ` Imre Deak [this message]
2020-01-06 14:34 ` [PATCH v6 2/4] drm/bridge: Patch atomic hooks to take a drm_bridge_state Neil Armstrong
2020-01-06 14:40 ` Boris Brezillon
2020-01-06 14:46 ` Neil Armstrong
2020-01-06 14:34 ` [PATCH v6 3/4] drm/bridge: Add an ->atomic_check() hook Neil Armstrong
2020-01-06 14:34 ` [PATCH v6 4/4] drm/bridge: Add the necessary bits to support bus format negotiation Neil Armstrong
2020-01-06 22:30 ` Jonas Karlman
2020-01-06 14:37 ` [PATCH v6 0/4] drm: Add support for bus-format negotiation Boris Brezillon
2020-01-07 9:24 ` Neil Armstrong
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=20200107144605.GD29830@ideak-desk.fi.intel.com \
--to=imre.deak@intel.com \
--cc=andrew.smirnov@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=cphealy@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@siol.net \
--cc=jonas@kwiboo.se \
--cc=kernel@collabora.com \
--cc=kyungmin.park@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=mark.rutland@arm.com \
--cc=narmstrong@baylibre.com \
--cc=nikita.yoush@cogentembedded.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=sw0312.kim@samsung.com \
--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