From: Paul Mundt <lethal@linux-sh.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 0/2 v2] runtime PM for the sh-mobile MIPI DSI driver
Date: Wed, 05 Jan 2011 08:33:18 +0000 [thread overview]
Message-ID: <20110105083318.GE23889@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1012271115470.669@axis700.grange>
On Mon, Dec 27, 2010 at 11:23:02AM +0100, Guennadi Liakhovetski wrote:
> This is v2 of the patch series, implementing runtime-pm for the sh-mobile
> mipi-dsi driver and removing the static clock configuration on the AP4EVB
> board.
On Wed, Dec 29, 2010 at 09:12:18AM +0100, Guennadi Liakhovetski wrote:
> These patches teach the sh-mobile MIPI DSI driver to use platform data to
> support different SoC with register layout variations and different LCD
> panels. Two of these patches affect the actual driver and one - currently
> its only user - the ap4evb board. To avoid compilation and run-time
> regressions we have to first add new gields to the header, then set them
> in the affected platform, and only then modify the driver to use them.
> This produces an unpleasant dependency chain. Alternatively, all these
> patches could be merged into one, but that would span multiple subsystems.
> I leave it to the maintainer to decide:)
I've merged both of these patch series in to the common/fdev-mipi branch
in the SH/R-Mobile tree and then merged that topic branch in to the fbdev
tree. Both needed a bit of mangling to merge on top of Magnus's earlier
patches, so you may want to verify that I haven't broken anything
accidentally.
prev parent reply other threads:[~2011-01-05 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 10:23 [PATCH 0/2 v2] runtime PM for the sh-mobile MIPI DSI driver Guennadi Liakhovetski
2010-12-28 9:43 ` Magnus Damm
2011-01-05 8:33 ` Paul Mundt [this message]
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=20110105083318.GE23889@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-fbdev@vger.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.