audio: a2220: Fix the wrong GPIO for reset
authorBo Yan <byan@nvidia.com>
Sat, 8 Dec 2012 03:06:31 +0000 (19:06 -0800)
committerMandar Padmawar <mpadmawar@nvidia.com>
Tue, 19 Feb 2013 06:27:51 +0000 (22:27 -0800)
commit8713f8e1b46c046487fb65bb1fc1c7b645d2f08f
treeaf2106b04fd37706d46d924078ca28abefacbf81
parentb37127d1c36d643bbc46c29dbcea518fb32ea807
audio: a2220: Fix the wrong GPIO for reset

gpio number for reset is not specified in platform data, in fact, its
value is 0 after kzalloc.  Requesting gpio for this number is bad
because the pin for GPIO 0 is used for other purposes. The original
hack is to use a magic number 118 for reset GPIO, this still needs to
be fixed. Meanwhile, to unblock the work which requires GPIO 0,
do not request GPIO 0 in this module.

Change-Id: Ibe1c38e948603fcd1d9de1164d5f69b0804757d2
Signed-off-by: Bo Yan <byan@nvidia.com>
Reviewed-on: http://git-master/r/169562
(cherry picked from commit 2cf6fa583d1eb1f993cd1b7b5fe9cab8fcc55fb3)
Reviewed-on: http://git-master/r/201516
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Dara Ramesh <dramesh@nvidia.com>
Reviewed-by: Vijay Mali <vmali@nvidia.com>
drivers/misc/a2220.c