From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: airlied@linux.ie, dri-devel@lists.freedesktop.org,
linux-acpi@vger.kernel.org
Subject: [PATCH 00/13] More GMA500 work
Date: Wed, 02 May 2012 19:12:20 +0100 [thread overview]
Message-ID: <20120502181044.26650.40123.stgit@bluebook> (raw)
This follows on from the last set and sorts out the lid regression
they caused on the Poulsbo devices. It then includes another pile
of clean up work and Medfield fixes from Kirill.
---
Alan Cox (1):
gma500: address the lid code
Kirill A. Shutemov (12):
gma500: mdfld_dsi_dpi_mode_set() do not corrupt DSPSTRIDE
gma500: mid-bios: rewrite VBT/GCT handling in a cleaner way
gma500: fix -Wmissing-include-dirs warnings
gma500: cdv_intel_lvds: mark cdv_intel_lvds_enc_funcs as static
gma500: oaktrail_hdmi_i2c_handler(): base should be __iomem
gma500: lid_state should be __iomem
gma500: psb_irq_turn_off_dpst() fix bit operation
gma500: framebuffer: mark psb_fb_helper_funcs as static
gma500: vram_addr should be __iomem
gma500: sgx_reg and vdc_reg should be __iomem
gma500: gtt: fix __iomem sparse warnings
gma500: psb_gtt_init(): drop unused variable
drivers/gpu/drm/gma500/Makefile | 2
drivers/gpu/drm/gma500/cdv_intel_lvds.c | 2
drivers/gpu/drm/gma500/framebuffer.c | 5
drivers/gpu/drm/gma500/gtt.c | 14 +
drivers/gpu/drm/gma500/mdfld_dsi_dpi.c | 1
drivers/gpu/drm/gma500/mid_bios.c | 295 ++++++++++++++++++----------
drivers/gpu/drm/gma500/oaktrail.h | 25 +-
drivers/gpu/drm/gma500/oaktrail_device.c | 8 -
drivers/gpu/drm/gma500/oaktrail_hdmi_i2c.c | 2
drivers/gpu/drm/gma500/oaktrail_lvds.c | 4
drivers/gpu/drm/gma500/opregion.c | 2
drivers/gpu/drm/gma500/psb_drv.c | 2
drivers/gpu/drm/gma500/psb_drv.h | 11 -
drivers/gpu/drm/gma500/psb_irq.c | 2
drivers/gpu/drm/gma500/psb_lid.c | 2
15 files changed, 224 insertions(+), 153 deletions(-)
--
#include <witty.h>
next reply other threads:[~2012-05-02 18:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 18:12 Alan Cox [this message]
2012-05-02 18:12 ` [PATCH 01/13] gma500: address the lid code Alan Cox
2012-05-02 18:13 ` [PATCH 02/13] gma500: psb_gtt_init(): drop unused variable Alan Cox
2012-05-02 18:13 ` [PATCH 03/13] gma500: gtt: fix __iomem sparse warnings Alan Cox
2012-05-02 18:13 ` [PATCH 04/13] gma500: sgx_reg and vdc_reg should be __iomem Alan Cox
2012-05-02 18:13 ` [PATCH 05/13] gma500: vram_addr " Alan Cox
2012-05-02 18:14 ` [PATCH 06/13] gma500: framebuffer: mark psb_fb_helper_funcs as static Alan Cox
2012-05-02 18:14 ` [PATCH 07/13] gma500: psb_irq_turn_off_dpst() fix bit operation Alan Cox
2012-05-02 18:14 ` [PATCH 08/13] gma500: lid_state should be __iomem Alan Cox
2012-05-02 18:16 ` [PATCH 09/13] gma500: oaktrail_hdmi_i2c_handler(): base " Alan Cox
2012-05-02 18:16 ` [PATCH 10/13] gma500: cdv_intel_lvds: mark cdv_intel_lvds_enc_funcs as static Alan Cox
2012-05-02 18:16 ` [PATCH 11/13] gma500: fix -Wmissing-include-dirs warnings Alan Cox
2012-05-02 18:17 ` [PATCH 12/13] gma500: mid-bios: rewrite VBT/GCT handling in a cleaner way Alan Cox
2012-05-02 18:17 ` [PATCH 13/13] gma500: mdfld_dsi_dpi_mode_set() do not corrupt DSPSTRIDE Alan Cox
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=20120502181044.26650.40123.stgit@bluebook \
--to=alan@lxorguk.ukuu.org.uk \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-acpi@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 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).