Hi, On Thu, 2011-02-17 at 08:11 +0000, Bryan Wu wrote: > From: Mathieu J. Poirier <mathieu.poirier@xxxxxxxxxxxxx> > > https://bugs.launchpad.net/bugs/630885 > > When booting, the omapdss subsystem is looking for a regulator named > "vdds_sdi". When the regulator is not found the initialisation sequence > is aborted resulting in omapfb not finding a display to work with. This > patch allows the omapfb sub system to complete its initialisation > properly and enable LCD display. The problem was fixed by lumping a > "vdds_sdi" with the already existing "vdds_dsi" regulator. This fix > takes its root from work done on the Beagle board and the Pandora board. This isn't a correct fix. If we would add the sdi regulator to remove the problem we would need to add the sdi regulator to all boards, not just EVM. However, I wouldn't go adding them. The proper fix is to make sdi.c only use the regulator if SDI is actually used. Currently it tries to acquire it always. A simple "fix" for this is to disable SDI from Kconfig, presuming you don't have boards that use SDI interface. N900 is the only board that I know of which uses SDI. Tomi -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
