Hi,
On Mon, Feb 28, 2011 at 15:45, Michael Buesch <[email protected]> wrote:
> The n810 LCD does not work on the 2.6.38(-rc6) kernel
> due to changes in the OMAP GPIO-hwmod code.
>
> The hwmod code performs a soft-reset on the GPIO
> module. The first GPIO module carries the MIPID
> "nreset" line, which is toggled due to the hwmod soft reset.
> This resets Blizzard and breaks it, because
> it assumes the LCD was left in the state that the
> bootloader initialized it to:
It is the design of hwmod framework that all the omap devices
should be reset independent of bootloader settings. The
corresponding board file/ the driver should take care of init settings
of the device based on the requirement. Avoid dependency on
bootloader.
>
> if (!(blizzard_read_reg(BLIZZARD_PLL_DIV) & 0x80)) {
> dev_err(fbdev->dev,
> "controller not initialized by the bootloader\n");
> r = -ENODEV;
> goto err3;
> }
>
> My temporary workaround to this issue is to disable
> soft reset for the first GPIO module:
>
> static struct omap_hwmod omap2420_gpio1_hwmod = {
> .name = "gpio1",
> .flags = HWMOD_INIT_NO_RESET, /* Workaround: Don't
> reset the n810 MIPID */
NACK.
As the problem is specific to the board settings, this shall be handled
in the board file itself.
>
> I'm wondering if a better fix suitable for the mainline
> kernel inclusion could be found.
> Any ideas?
Re-initialize the "nreset" line of the Blizzard in the
corresponding board file.
- V Charulatha
>
> --
> Greetings, Michael.
>
>
>
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
