Re: [PATCH v4 00/18] MFD/ASoC/Input: TWL4030/TWL60X0 changes
From: Péter Ujfalusi
Date: Fri Jun 17 2011 - 05:02:27 EST
Hello Tony, Samuel, Mark, Liam.
Did you got time to check the patches for your areas?
I want to send the updated series with the change in the vibra driver
(addressing comments from Dmitry, and Tejun), but I want to address your
comments as well at the same time if any (or add you Ack).
On Friday 10 June 2011 13:54:18 Ujfalusi, Peter wrote:
> Changes since v3:
> - patches generated with git format-patch -M to handle renames better
> - Included depending updates for twl6040 soc codec driver:
> - HS ramp configuration, new ABE dais, updated sample rate constraints
> - Configure the twl6040 codec on SDP4430 board
> Updated intro message from the v3 series:
> The series will do five major things, and they are in one series, because
> they pretty much depending on each other, so it is easier to handle them
> 1. Move the common pmic related configurations out from the board files.
> New twl-common.c/h file has been created for this purpose.
> OMAP3 board files received two patches (pdata, and regualtor changes), OMAP4
> board files has been changed with one patch.
> 2. Rename the twl4030-codec MFD driver to twl4030-audio
> Since the ASoC multicomponent introduction (2.6.37) the twl4030-codec MFD
> dirver had been using twl4030-audio to register (twl4030-codec is the ASoC
> codec driver). The documentation refers to this part of twl as audio block,
> so it is better to rename the driver as well to avoid confusion.
> 3. Introduction of MFD driver for twl6040.
> The TWL6040 audio IC has codec and vibra functionality.
> Convert the existing ASoC codec driver to use the new MFD driver's
> 4. Vibrator driver for TWL6040 (Input/ForceFeedback driver)
> The driver itself, and support for the vibrators in SDP4430 board.
> 5. Updates for twl6040 ASoC codec driver
> HS ramp configuration, new ABE dais, updated sample rate constraints,
> SDP4430 configuration.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/