All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen-Yu Tsai <wens@csie.org>
To: Maxime Ripard <maxime.ripard@free-electrons.com>,
	David Airlie <airlied@linux.ie>, Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>
Cc: Chen-Yu Tsai <wens@csie.org>,
	dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com
Subject: [PATCH 0/2] drm/sun4i: Add display backend interrupt to dt binding
Date: Mon, 27 Mar 2017 22:38:45 +0800	[thread overview]
Message-ID: <20170327143847.16259-1-wens@csie.org> (raw)

Hi Maxime,

As promised, here is the patch adding the interrupt line for the display
backend to the sun5i shared dtsi, and another one adding it to the device
tree bindings.

The display backend has an undocumented (in the user manual) interrupt
that, according to vendor code, is raised when the current scanout is
completed. This might be a better fit for DRM/KMS vblank signalling,
rather than the TCON's vblank interrupt. If true, it would allow us
to cut out the TCON from the crtc in the driver, instead keeping it
solely as an encoder, simplifying some of the inter-component code.

Regardless, the interrupt line exists and should be added to the
device tree.


Regards
ChenYu

Chen-Yu Tsai (2):
  drm/sun4i: Add display backend interrupt to device tree binding
  ARM: dts: sun5i: Add interrupt for display backend

 Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt | 2 ++
 arch/arm/boot/dts/sun5i.dtsi                                  | 1 +
 2 files changed, 3 insertions(+)

-- 
2.11.0

WARNING: multiple messages have this Message-ID (diff)
From: Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>
To: Maxime Ripard
	<maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
	David Airlie <airlied-cv59FeDIM0c@public.gmane.org>,
	Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
Cc: Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>,
	dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: [PATCH 0/2] drm/sun4i: Add display backend interrupt to dt binding
Date: Mon, 27 Mar 2017 22:38:45 +0800	[thread overview]
Message-ID: <20170327143847.16259-1-wens@csie.org> (raw)

Hi Maxime,

As promised, here is the patch adding the interrupt line for the display
backend to the sun5i shared dtsi, and another one adding it to the device
tree bindings.

The display backend has an undocumented (in the user manual) interrupt
that, according to vendor code, is raised when the current scanout is
completed. This might be a better fit for DRM/KMS vblank signalling,
rather than the TCON's vblank interrupt. If true, it would allow us
to cut out the TCON from the crtc in the driver, instead keeping it
solely as an encoder, simplifying some of the inter-component code.

Regardless, the interrupt line exists and should be added to the
device tree.


Regards
ChenYu

Chen-Yu Tsai (2):
  drm/sun4i: Add display backend interrupt to device tree binding
  ARM: dts: sun5i: Add interrupt for display backend

 Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt | 2 ++
 arch/arm/boot/dts/sun5i.dtsi                                  | 1 +
 2 files changed, 3 insertions(+)

-- 
2.11.0

WARNING: multiple messages have this Message-ID (diff)
From: wens@csie.org (Chen-Yu Tsai)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] drm/sun4i: Add display backend interrupt to dt binding
Date: Mon, 27 Mar 2017 22:38:45 +0800	[thread overview]
Message-ID: <20170327143847.16259-1-wens@csie.org> (raw)

Hi Maxime,

As promised, here is the patch adding the interrupt line for the display
backend to the sun5i shared dtsi, and another one adding it to the device
tree bindings.

The display backend has an undocumented (in the user manual) interrupt
that, according to vendor code, is raised when the current scanout is
completed. This might be a better fit for DRM/KMS vblank signalling,
rather than the TCON's vblank interrupt. If true, it would allow us
to cut out the TCON from the crtc in the driver, instead keeping it
solely as an encoder, simplifying some of the inter-component code.

Regardless, the interrupt line exists and should be added to the
device tree.


Regards
ChenYu

Chen-Yu Tsai (2):
  drm/sun4i: Add display backend interrupt to device tree binding
  ARM: dts: sun5i: Add interrupt for display backend

 Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt | 2 ++
 arch/arm/boot/dts/sun5i.dtsi                                  | 1 +
 2 files changed, 3 insertions(+)

-- 
2.11.0

             reply	other threads:[~2017-03-27 14:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27 14:38 Chen-Yu Tsai [this message]
2017-03-27 14:38 ` [PATCH 0/2] drm/sun4i: Add display backend interrupt to dt binding Chen-Yu Tsai
2017-03-27 14:38 ` Chen-Yu Tsai
2017-03-27 14:38 ` [PATCH 1/2] drm/sun4i: Add display backend interrupt to device tree binding Chen-Yu Tsai
2017-03-27 14:38   ` Chen-Yu Tsai
2017-03-27 14:38   ` Chen-Yu Tsai
2017-03-29  7:09   ` Maxime Ripard
2017-03-29  7:09     ` Maxime Ripard
2017-03-29  7:09     ` Maxime Ripard
2017-04-03 13:24   ` Rob Herring
2017-04-03 13:24     ` Rob Herring
2017-04-03 13:24     ` Rob Herring
2017-03-27 14:38 ` [PATCH 2/2] ARM: dts: sun5i: Add interrupt for display backend Chen-Yu Tsai
2017-03-27 14:38   ` Chen-Yu Tsai
2017-03-27 14:38   ` Chen-Yu Tsai
2017-03-29  7:13   ` Maxime Ripard
2017-03-29  7:13     ` Maxime Ripard
2017-03-29  7:13     ` Maxime Ripard
2017-03-29  7:26     ` Chen-Yu Tsai
2017-03-29  7:26       ` Chen-Yu Tsai
2017-03-29  7:26       ` Chen-Yu Tsai

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=20170327143847.16259-1-wens@csie.org \
    --to=wens@csie.org \
    --cc=airlied@linux.ie \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=mark.rutland@arm.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=robh+dt@kernel.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.