- 05 Apr, 2011 40 commits
-
-
Alan Cox authored
Signed-off-by:
Alan Cox <alan@linux.intel.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@suse.de>
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
Zap... bang And take out a few more variables that are now dead Signed-off-by:
-
Alan Cox authored
Keep this as its own commit for bisection purposes Signed-off-by:
-
Justin P. Mattock authored
The patch below removes an extra semi-colon from various parts of the kernel. Please have a look when you have time, and let me know if its legit or not. Signed-off-by:
Justin P. Mattock <justinmattock@gmail.com> Signed-off-by:
-
Alan Cox authored
We are not using TTM, we are not going to use TTM either Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
We don't need the 3D validation stuff so it and all the related gunge can depart. While we are at it prune some unused definitions. Signed-off-by:
-
Alan Cox authored
The camera interface is also not covered (and we won't be using TTM anyway even if it ever re-emerges) so it to can go Signed-off-by:
-
Alan Cox authored
RAR registers are used on MID platforms for various protected video playback activities using video playback engines we don't support. So Rasputin can keep his Rars Signed-off-by:
-
Alan Cox authored
Turn it on, turn it up, turn it loose Signed-off-by:
-
Alan Cox authored
Grovel the firmware via the Moorestown interfaces and read the other bits off the fuses. Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
For Moorestown we want to use the mrst LVDS setup not the Poulsbo setup Signed-off-by:
-
Alan Cox authored
Which is of course different to Poulsbo. Signed-off-by:
-
Alan Cox authored
Build the new files now all the changes they need are present. They won't yet be used but the plumbing is next step. Signed-off-by:
-
Alan Cox authored
Moorestown needs somewhere to stash various pipe config registers and the firmware and fuse configurations Signed-off-by:
-
Alan Cox authored
We have a set of firmware passed descriptors and things we need to grovel through for video configuration. This differs from the setup for the PC style Poulsbo hardware. Signed-off-by:
-
Alan Cox authored
We need these as they are also used by the Moorestown LVDS display support. Make the various needed symbols visible in the headers Signed-off-by:
-
Alan Cox authored
Add the new files needed for the GMA500 driver to support Moorestown LVDS displays. Don't wire them in yet. Signed-off-by:
-
Alan Cox authored
The Moorestown systems have some graphics differences we care about and some we don't need to. To start with it has a single pipe and that pipe can be used for LVDS Signed-off-by:
-
Luis R. Rodriguez authored
This was empty code, WTF^pi. Cc: Naveen Singh <nsingh@atheros.com> Signed-off-by:
Luis R. Rodriguez <lrodriguez@atheros.com> Signed-off-by:
-
Luis R. Rodriguez authored
These do not help in any way. Cc: Naveen Singh <nsingh@atheros.com> Signed-off-by:
-
Luis R. Rodriguez authored
This has no functional changes. Cc: Naveen Singh <nsingh@atheros.com> Signed-off-by:
-
Luis R. Rodriguez authored
There should be no need to assign the pm ops dynamically, so assign them statically and make them const. While we are doing this just do some simple code style cleanup on the routines and move them above prior to their assignment into the driver ops. This has no functional change other than assigning the pm ops statically. Cc: Naveen Singh <nsingh@atheros.com> Signed-off-by:
-
Luis R. Rodriguez authored
Perhaps there was some good intention on having some platform driver on ath6kl, but right now its pointless. Kill! Cc: Naveen Singh <nsingh@atheros.com> Signed-off-by:
-
Luis R. Rodriguez authored
No functional changes except renames of the routines and id data structure. Cc: Naveen Singh <nsingh@atheros.com> Signed-off-by:
-
Luis R. Rodriguez authored
Removes verbose debug messages and checks that are just not needed, and renames the functions to something more sensible. While we clean this up, just move the routines above and remove the forward declarations. Cc: Naveen Singh <nsingh@atheros.com> Signed-off-by:
-
Luis R. Rodriguez authored
This will be passed along to the SDIO probe routine when it fails. This will generate better error code to the user when loading the module if it fails. Cc: Naveen Singh <nsingh@atheros.com> Signed-off-by:
-
Luis R. Rodriguez authored
These map to do nothing. Cc: Naveen Singh <nsingh@atheros.com> Signed-off-by:
-
Luis R. Rodriguez authored
This propagates initial platform registration failures and also HIF initialization failures. Cc: Naveen Singh <nsingh@atheros.com> Signed-off-by:
-
Luis R. Rodriguez authored
Make the code more legible by parsing the config options on the header file. While a it ensure to propagate errors and bail out if we fail to set btcoex params. Cc: Naveen Singh <nsingh@atheros.com> Signed-off-by:
-
Luis R. Rodriguez authored
When CONFIG_ATH6KL_ENABLE_COEXISTENCE gets enabled we define another flag called ENABLE_COEXISTENCE, just use CONFIG_ATH6KL_ENABLE_COEXISTENCE since that is already defined by the generated autoconf header file from the kernel. Cc: Naveen Singh <nsingh@atheros.com> Signed-off-by:
-
Luis R. Rodriguez authored
There already is a CONFIG_AR600x_CUSTOM_XXX if this is desired to be used. Cc: Naveen Singh <nsingh@atheros.com> Signed-off-by:
-
Luis R. Rodriguez authored
When CONFIG_AR600x_SD32_XXX gets enabled we define another flag called AR600x_SD32_XXX, just use CONFIG_AR600x_SD32_XXX since that is already defined by the generated autoconf header file from the kernel. Cc: Naveen Singh <nsingh@atheros.com> Signed-off-by:
-
Luis R. Rodriguez authored
When CONFIG_AR600x_WB31_XXX gets enabled we define another flag called AR600x_WB31_XXX, just use CONFIG_AR600x_WB31_XXX since that is already defined by the generated autoconf header file from the kernel. Cc: Naveen Singh <nsingh@atheros.com> Signed-off-by:
-
Luis R. Rodriguez authored
When CONFIG_AR600x_SD31_XXX gets enabled we define another flag called AR600x_SD31_XXX, just use CONFIG_AR600x_SD31_XXX since that is already defined by the generated autoconf header file from the kernel. Cc: Naveen Singh <nsingh@atheros.com> Signed-off-by:
-
