From: Russell King - ARM Linux <linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org>
To: Liviu Dudau <liviu.dudau-5wv7dgnIgG8@public.gmane.org>
Cc: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
David Airlie <airlied-cv59FeDIM0c@public.gmane.org>,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Mali DP Maintainers
<malidp-VeJGdqYn5oNWk0Htik3J/w@public.gmane.org>,
Brian Starkey <brian.starkey-5wv7dgnIgG8@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] drm: hdlcd: allow HDLCD to be used without interrupt
Date: Wed, 26 Jul 2017 11:27:48 +0100 [thread overview]
Message-ID: <20170726102748.GM31807@n2100.armlinux.org.uk> (raw)
In-Reply-To: <E1daJCF-0003pG-DI-eh5Bv4kxaXIk46pC+1QYvQNdhmdF6hFW@public.gmane.org>
On Wed, Jul 26, 2017 at 11:05:39AM +0100, Russell King wrote:
> Some ARM platforms do not wire the HDLCD interrupt. Allow hdlcd to
> initialise without an interrupt present.
>
> Signed-off-by: Russell King <rmk+kernel-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org>
This isn't fully functional on ARM MPS platforms yet, but at least
gets us further. Without any display connected:
[ 14.315986] [drm] found ARM HDLCD version r0p0
[ 14.557038] tda998x 2-0070: found TDA19988
[ 14.622232] hdlcd 40205000.hdlcd: bound 2-0070 (ops 0x213534)
[ 14.630406] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 14.639335] [drm] No driver support for vblank timestamp query.
[ 14.653210] [drm] Cannot find any crtc or sizes - going 1024x768
[ 15.232556] hdlcd 40205000.hdlcd: fb0: frame buffer device
[ 15.284076] [drm] Initialized hdlcd 1.0.0 20151021 for 40205000.hdlcd on minor 0
With a TV connected, the driver doesn't initialise:
[ 14.422810] [drm] found ARM HDLCD version r0p0
[ 14.657227] tda998x 2-0070: found TDA19988
[ 14.722439] hdlcd 40205000.hdlcd: bound 2-0070 (ops 0x213534)
[ 14.730613] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 14.739538] [drm] No driver support for vblank timestamp query.
[ 15.311977] hdlcd 40205000.hdlcd: Failed to set initial hw configuration.
[ 15.357402] hdlcd 40205000.hdlcd: master bind failed: -12
[ 15.365082] tda998x: probe of 2-0070 failed with error -12
I don't think this is correct behaviour - if we fail to set an initial
configuration (which will be based on the resolution of the connected
display) why should the driver fail to probe - it's not that there is
no device, it's (in this case) that there aren't the resources for the
chosen mode. Userspace could always try setting a different mode.
I suspect the above failure is down to either (a) not having enough
memory available to allocate a 1920x1080 frame buffer, or (b) not
(yet) being able to program the hdlcd pixel clock for this platform,
which is currently hard-coded in DT at 23.75MHz.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-07-26 10:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 10:05 [PATCH] drm: hdlcd: allow HDLCD to be used without interrupt Russell King
[not found] ` <E1daJCF-0003pG-DI-eh5Bv4kxaXIk46pC+1QYvQNdhmdF6hFW@public.gmane.org>
2017-07-26 10:27 ` Russell King - ARM Linux [this message]
[not found] ` <20170726102748.GM31807-l+eeeJia6m9URfEZ8mYm6t73F7V6hmMc@public.gmane.org>
2017-07-28 15:23 ` Liviu Dudau
[not found] ` <20170728152311.GA970-A/Nd4k6kWRHZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2017-07-28 15:58 ` Russell King - ARM Linux
[not found] ` <20170728155827.GV31807-l+eeeJia6m9URfEZ8mYm6t73F7V6hmMc@public.gmane.org>
2017-07-28 16:32 ` Liviu Dudau
2017-08-29 13:33 ` Liviu Dudau
[not found] ` <20170829133351.GK10796-A/Nd4k6kWRHZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2017-08-29 16:48 ` Russell King - ARM Linux
[not found] ` <20170829164824.GH20805-l+eeeJia6m9URfEZ8mYm6t73F7V6hmMc@public.gmane.org>
2017-08-30 10:54 ` Liviu Dudau
[not found] ` <20170830105414.GB1310-A/Nd4k6kWRHZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2017-08-30 11:13 ` Russell King - ARM Linux
2017-08-10 12:15 ` Vladimir Murzin
[not found] ` <e68186a4-2435-a969-7eff-21556d6a6b03-5wv7dgnIgG8@public.gmane.org>
2017-08-21 14:45 ` Vladimir Murzin
[not found] ` <9cdccb9c-83c5-5867-06a5-3b344102d232-5wv7dgnIgG8@public.gmane.org>
2017-08-24 10:16 ` Liviu Dudau
2017-08-03 18:55 ` Rob Herring
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=20170726102748.GM31807@n2100.armlinux.org.uk \
--to=linux-i+ivw8tiwo2tmtq+vha3yw@public.gmane.org \
--cc=airlied-cv59FeDIM0c@public.gmane.org \
--cc=brian.starkey-5wv7dgnIgG8@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=liviu.dudau-5wv7dgnIgG8@public.gmane.org \
--cc=malidp-VeJGdqYn5oNWk0Htik3J/w@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@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 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).