From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Liviu.Dudau@arm.com
Cc: dri-devel@lists.freedesktop.org, tomi.valkeinen@ti.com,
Jyri Sarha <jsarha@ti.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] drm/i2c: tda998x: Choose between atomic or non atomic dpms helper
Date: Mon, 18 Jan 2016 11:15:05 +0000 [thread overview]
Message-ID: <20160118111504.GG5783@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20160118095226.GK13633@e106497-lin.cambridge.arm.com>
On Mon, Jan 18, 2016 at 09:52:27AM +0000, Liviu.Dudau@arm.com wrote:
> On Sat, Jan 16, 2016 at 10:17:54PM +0200, Jyri Sarha wrote:
> > It just makes me wonder if drm_atomic_helper_connector_dpms() should
> > call the legacy callback automatically if DRIVER_ATOMIC is not set or
> > at least bail out gracefully with an error message. Then again it may
> > be overkill if the tda998x is the only driver that need to support
> > both situations.
>
> I would guess that in general it makes sense for the core code to do what
> you suggest, but the idea is to try to encourage the drivers to convert
> to atomic ops rather than give them too many crutches. And the tda998x will
> need this for a short period of time until tilcdc converts as well.
It's not just tilcdc that this driver is used by.
I have no plans at present to convert armada to atomic mode setting,
although I occasionally push it (I hope) towards that goal. This
isn't going to happen quickly, because I've other areas that need
work too.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-01-18 11:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-16 20:17 [PATCH] drm/i2c: tda998x: Choose between atomic or non atomic dpms helper Jyri Sarha
2016-01-18 9:52 ` Liviu.Dudau
2016-01-18 11:15 ` Russell King - ARM Linux [this message]
2016-02-25 10:09 ` Jyri Sarha
2016-02-25 10:20 ` Liviu.Dudau
2016-03-07 21:47 ` Jyri Sarha
2016-03-08 1:16 ` Dave Airlie
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=20160118111504.GG5783@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=Liviu.Dudau@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.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).