On Wed, 2012-09-19 at 15:53 -0400, Raphaël Assénat wrote: > Hello Tomi, > > On 21/08/12 06:39 AM, Tomi Valkeinen wrote: > > Hi, > > > > On Wed, 2012-08-15 at 15:16 -0400, Raphael Assenat wrote: > >> On our AM3505 based board, dpi.c complains that there is no VDSS_DSI regulator > >> and the framebuffer cannot be enabled. However, this check does not seem to > >> apply to AM3505/17 chips. > >> > >> Taking into account comments received after my first patch[1], I have added > >> entries to dss_features.c to support the am35xx soc. Then in dpi.c, instead > >> of using cpu_is_omap34xx() and soc_is_am35xx(), a call to dss_has_feature() > >> is used. > >> > >> [1] http://marc.info/?l=linux-fbdev&m=134272967203409&w=2 > >> > >> Signed-off-by: Raphaël Assénat <raph@xxxxxx> > > > > Chandrabhanu has posted a series that removes a bunch of cpu_is checks > > from omapdss. On of them is the use of VDDS_DSI in dpi.c. > > > > Can you wait until I've merged those patches to omapdss master branch > > (probably a few days), and then create a new patch that adds AM35xx to > > dss_features? > > Please find a new version of the patch below. Due to the above mentioned changes, > the patch now only touches dss_features.c. > > Tested on am3505 only. > > Diff based on git://gitorious.org/linux-omap-dss2/linux.git master. Thanks, I'll apply this. Tomi
Attachment:
signature.asc
Description: This is a digitally signed message part
