From mboxrd@z Thu Jan 1 00:00:00 1970 From: Raphael Assenat Subject: [PATCH v2] OMAPDSS: Do not require a VDDS_DSI regulator on am35xx Date: Wed, 15 Aug 2012 15:16:27 -0400 Message-ID: <20120815191627.GA22993@renkinjitsu.usine.8d.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from roc.holo.8d.com ([64.254.227.115]:54611 "EHLO roc.holo.8d.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753873Ab2HOTQa (ORCPT ); Wed, 15 Aug 2012 15:16:30 -0400 Content-Disposition: inline Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: linux-omap@vger.kernel.org Cc: tomi.valkeinen@ti.com On our AM3505 based board, dpi.c complains that there is no VDSS_DSI re= gulator and the framebuffer cannot be enabled. However, this check does not see= m to apply to AM3505/17 chips. Taking into account comments received after my first patch[1], I have a= dded entries to dss_features.c to support the am35xx soc. Then in dpi.c, ins= tead of using cpu_is_omap34xx() and soc_is_am35xx(), a call to dss_has_featu= re() is used. [1] http://marc.info/?l=3Dlinux-fbdev&m=3D134272967203409&w=3D2 Signed-off-by: Rapha=EBl Ass=E9nat diff --git a/drivers/video/omap2/dss/dpi.c b/drivers/video/omap2/dss/dp= i.c index 3266be2..0e83054 100644 --- a/drivers/video/omap2/dss/dpi.c +++ b/drivers/video/omap2/dss/dpi.c @@ -31,9 +31,9 @@ #include =20 #include