Re: [PATCH] omap3: Fix 3630 mux errors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Tony Lindgren <tony@xxxxxxxxxxx> [100429 11:20]:
> * Manjunatha GK <manjugk@xxxxxx> [100429 00:23]:
> > From: Allen Pais <allen.pais@xxxxxx>
> > 
> > The omap3630 has more mux signals than 34xx. The additional
> > pins exist in omap36xx_cbp_subset, but are not initialized
> > as the superset is missing these offsets. This causes the
> > following errors during the boot:
> 
> I have an earlier version of this queued up, will take a look
> and see if they're the same:
> 
> https://patchwork.kernel.org/patch/87555/

Turns out these are all non-muxable pins. So the right fix
is to remove them from the 3630 ball table. Will post a patch
shortly for this along with my other fixes.

Regards,

Tony
--
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

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux