| commit | 2150dace47258722c67f297509bc6171e7b486ad | |
| author | Simon Horman <horms@verge.net.au> | |
| Fri, 7 Jan 2011 22:26:15 +0000 (7 22:26 +0000) | ||
| committer | Paul Mundt <lethal@linux-sh.org> | |
| Wed, 19 Jan 2011 03:14:05 +0000 (19 12:14 +0900) | ||
| tree | de2f5cf273286cf978fb439709afb16d4958a8be | treesnapshot (tar.gz zip) |
| parent | 5a1b70a48ccfca241016762dfe04b135b8915a1b | commitdiff |
ARM: mach-shmobile: mackerel: clarify shdi/mmcif switch settings
* Pins 2 and 4 of switch 33 are documented as don't care on the PCB,
my testing seems to confirm this.
* I have been unable to do anything sensible with S1 set to on.
Am I missing something with regards to MMC1?
* Clarify which driver is needed for each switch setting.
* Should the AP4 board code be updated to allow the
SHDI driver to access SHDI1 as the mackerel code does?
Signed-off-by: Simon Horman <horms@verge.net.au>
Acked-by: Yusuke Goda <yusuke.goda.sx@renesas.com>
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
* Pins 2 and 4 of switch 33 are documented as don't care on the PCB,
my testing seems to confirm this.
* I have been unable to do anything sensible with S1 set to on.
Am I missing something with regards to MMC1?
* Clarify which driver is needed for each switch setting.
* Should the AP4 board code be updated to allow the
SHDI driver to access SHDI1 as the mackerel code does?
Signed-off-by: Simon Horman <horms@verge.net.au>
Acked-by: Yusuke Goda <yusuke.goda.sx@renesas.com>
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
| arch/arm/mach-shmobile/board-mackerel.c | diffblobblamehistory |