All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: dri-devel@lists.freedesktop.org
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>, linux-omap@vger.kernel.org
Subject: [PATCH/RFC 9/7] drm: omapdrm: Don't forward set_min_bus_tput() to no-op platform code
Date: Wed, 14 Dec 2016 03:58:01 +0200	[thread overview]
Message-ID: <1481680684-11585-2-git-send-email-laurent.pinchart@ideasonboard.com> (raw)
In-Reply-To: <1481680684-11585-1-git-send-email-laurent.pinchart@ideasonboard.com>

The OMAP implementation of the set_min_bus_tput() API is a no-op.
There's no point in forwarding the driver calls to the platform code.
Remove the use of the related platform data callback, but keep the
internal function as a reminder that the feature will need to be
implemented when the OMAP platform will provide support.

Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
---
 drivers/gpu/drm/omapdrm/dss/core.c | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/drivers/gpu/drm/omapdrm/dss/core.c b/drivers/gpu/drm/omapdrm/dss/core.c
index b173f2889819..5dfb79c02ab3 100644
--- a/drivers/gpu/drm/omapdrm/dss/core.c
+++ b/drivers/gpu/drm/omapdrm/dss/core.c
@@ -78,12 +78,8 @@ struct platform_device *dss_get_core_pdev(void)
 
 int dss_set_min_bus_tput(struct device *dev, unsigned long tput)
 {
-	struct omap_dss_board_info *pdata = core.pdev->dev.platform_data;
-
-	if (pdata->set_min_bus_tput)
-		return pdata->set_min_bus_tput(dev, tput);
-	else
-		return 0;
+	/* To be implemented when the OMAP platform provides this feature. */
+	return 0;
 }
 
 #if defined(CONFIG_OMAP2_DSS_DEBUGFS)
-- 
Regards,

Laurent Pinchart

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-12-14  1:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-13 23:38 [PATCH/RFC 0/7] Remove the omapdrm device from platform code Laurent Pinchart
2016-12-13 23:38 ` [PATCH/RFC 1/7] drm: omapdrm: Add OMAP revision to omapdss platform data Laurent Pinchart
2016-12-13 23:38 ` [PATCH/RFC 2/7] ARM: OMAP2+: Populate the omapdss platform data OMAP revision Laurent Pinchart
2016-12-13 23:38 ` [PATCH/RFC 3/7] drm: omapdrm: Retrieve OMAP revision from omapdss Laurent Pinchart
2016-12-13 23:38 ` [PATCH/RFC 4/7] ARM: OMAP2+: Remove omapdrm platform data Laurent Pinchart
2016-12-13 23:38 ` [PATCH/RFC 5/7] drm: omapdrm: " Laurent Pinchart
2016-12-13 23:38 ` [PATCH/RFC 6/7] drm: omapdrm: Register omapdrm platform device in omapdss driver Laurent Pinchart
2016-12-14  8:20   ` Tomi Valkeinen
2016-12-14 11:54     ` Laurent Pinchart
2016-12-13 23:38 ` [PATCH/RFC 7/7] ARM: OMAP2+: Remove unused omapdrm platform device Laurent Pinchart
2016-12-14  1:58 ` [PATCH/RFC 8/7] drm: omapdrm: Handle DSI pin muxing internally Laurent Pinchart
2016-12-14  1:58   ` Laurent Pinchart [this message]
2016-12-14  1:58   ` [PATCH/RFC 10/7] ARM: OMAP2+: Remove DSI pin muxing Laurent Pinchart
2016-12-14  1:58   ` [PATCH/RFC 11/7] ARM: OMAP2+: Remove omapdss set_min_bus_tput platform data callback Laurent Pinchart
2016-12-14  1:58   ` [PATCH/RFC 12/7] drm: omapdrm: Remove unused omapdss platform data fields Laurent Pinchart
2016-12-18  0:54     ` [PATCH/RFC v1.1 12/7] drm: omapdrm: Remove unused omapdss platform data field Laurent Pinchart
2016-12-14 15:05 ` [PATCH/RFC 0/7] Remove the omapdrm device from platform code Tony Lindgren
2016-12-15  8:08   ` Tomi Valkeinen
2016-12-15 10:07     ` Laurent Pinchart
2016-12-15 11:04       ` Tomi Valkeinen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1481680684-11585-2-git-send-email-laurent.pinchart@ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tomi.valkeinen@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.