diff options
| author | Russell King <rmk+kernel@arm.linux.org.uk> | 2012-01-20 17:38:58 +0000 |
|---|---|---|
| committer | Russell King <rmk+kernel@arm.linux.org.uk> | 2012-01-20 17:38:58 +0000 |
| commit | 65f2e753f1eb09d3a7e2a0d16408a5433b4097b2 (patch) | |
| tree | 100066fa2d26930a490ee10bb191957f3b3e2df3 /mm/mempool.c | |
| parent | 216f63c41cac9f9f8f181fc19be399293c8c934e (diff) | |
| download | linux-65f2e753f1eb09d3a7e2a0d16408a5433b4097b2.tar.gz linux-65f2e753f1eb09d3a7e2a0d16408a5433b4097b2.tar.bz2 linux-65f2e753f1eb09d3a7e2a0d16408a5433b4097b2.zip | |
Revert "ARM: sa11x0: Implement autoloading of codec and codec pdata for mcp bus."
This reverts commit 5dd7bf59e0e8563265b3e5b33276099ef628fcc7.
Conflicts:
scripts/mod/file2alias.c
This change is wrong on many levels. First and foremost, it causes a
regression. On boot on Assabet, which this patch gives a codec id of
'ucb1x00', it gives:
ucb1x00 ID not found: 1005
0x1005 is a valid ID for the UCB1300 device.
Secondly, this patch is way over the top in terms of complexity. The
only device which has been seen to be connected with this MCP code is
the UCB1x00 (UCB1200, UCB1300 etc) devices, and they all use the same
driver. Adding a match table, requiring the codec string to match the
hardware ID read out of the ID register, etc is completely over the top
when we can just read the hardware ID register.
Diffstat (limited to 'mm/mempool.c')
0 files changed, 0 insertions, 0 deletions