[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110930033356.GA11621@kroah.com>
Date: Thu, 29 Sep 2011 20:33:56 -0700
From: Greg KH <greg@...ah.com>
To: Keith Packard <keithp@...thp.com>
Cc: Dave Airlie <airlied@...hat.com>, linux-kernel@...r.kernel.org,
dri-devel@...ts.freedesktop.org, intel-gfx@...ts.freedesktop.org
Subject: Re: [PATCH 00/24] MacBook Air patch sequence (v2)
On Thu, Sep 29, 2011 at 06:09:32PM -0700, Keith Packard wrote:
> Ok, so I've split all of the changes into bite-sized pieces so that
> they should make sense individually now. I've also added the same
> asynchronous power control to the panel power, this reduces the
> module load time down to about 700ms on my MacBook Air, which is
> pretty nice.
>
> Given the length of the series, I don't think this should all land in
> 3.1, however I'd like opinions on whether I should push this subset,
> which makes the MacBook Air work, into drm-intel-fixes and send that
> along.
>
> [PATCH 01/21] drm/i915: Enable digital port hotplug on PCH systems
> [PATCH 02/21] drm/i915: Shut down PCH interrupts during
> [PATCH 03/21] drm/i915: Remove extra 300ms delay during eDP mode
> [PATCH 04/21] drm/i915: Only use VBT panel mode on eDP if no EDID is
> [PATCH 05/21] drm/i915: Check eDP power when doing aux channel
> [PATCH 06/21] drm/i915: Unlock PCH_PP_CONTROL always
> [PATCH 07/21] drm/i915: Check for eDP inside
> [PATCH 08/21] drm/i915: Turn force VDD back off when panel running
> [PATCH 09/21] drm/i915: Delay DP i2c initialization until panel
> [PATCH 10/21] drm/i915: Wrap DP EDID fetch functions to enable eDP
> [PATCH 11/21] drm/i915: Enable eDP panel power during I2C
> [PATCH 12/21] drm/i915: Ensure eDP powered up during DP_SET_POWER
> [PATCH 13/21] drm/i915: Place long delays after each eDP VDD
> [PATCH 14/21] drm/i915: Correct eDP panel power sequencing delay
>
> The diffstat for that sequence is:
>
> i915_drv.h | 1
> i915_irq.c | 28 ++++++++
> i915_reg.h | 6 +
> intel_dp.c | 194 ++++++++++++++++++++++++++++++++++++++++++++++---------------
> 4 files changed, 180 insertions(+), 49 deletions(-)
>
> This might be too big at this point in the 3.1 release, so perhaps
> just marking these with a Cc: to stable would be more appropriate.
Are these really all -stable material?
I'm all for enabling new hardware like this, and overall, the patches
aren't that bad, just want to verify this.
And, I do have to tell you, "curses, now I have no excuse to not buy
that laptop!"
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists