public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Paul <seanpaul@chromium.org>
To: Vinod <vkoul@kernel.org>
Cc: devicetree@vger.kernel.org, ryadav@codeaurora.org,
	linux-arm-msm@vger.kernel.org,
	Sandeep Panda <spanda@codeaurora.org>,
	dri-devel@lists.freedesktop.org, abhinavk@codeaurora.org,
	hoegsberg@chromium.org, freedreno@lists.freedesktop.org,
	chandanu@codeaurora.org
Subject: Re: [PATCH v8 1/4] drm/bridge: add support for sn65dsi86 bridge driver
Date: Tue, 5 Jun 2018 18:32:47 -0400	[thread overview]
Message-ID: <20180605223247.GB3373@art_vandelay> (raw)
In-Reply-To: <20180605111715.GV16230@vkoul-mobl>

On Tue, Jun 05, 2018 at 04:47:15PM +0530, Vinod wrote:
> On 05-06-18, 11:10, Sandeep Panda wrote:
> > Add support for TI's sn65dsi86 dsi2edp bridge chip.
> > The chip converts DSI transmitted signal to eDP signal,
> > which is fed to the connected eDP panel.
> > 
> > This chip can be controlled via either i2c interface or
> > dsi interface. Currently in driver all the control registers
> > are being accessed through i2c interface only.
> > Also as of now HPD support has not been added to bridge
> > chip driver.
> > 
> > Changes in v1:
> >  - Split the dt-bindings and the driver support into separate patches
> >    (Andrzej Hajda).
> >  - Use of gpiod APIs to parse and configure gpios instead of obsolete ones
> >    (Andrzej Hajda).
> >  - Use macros to define the register offsets (Andrzej Hajda).
> 
> This is pretty useless for changelog. This is useful for review but not
> down the line when this is applied
> 
> Since you have cover letter, you may add it there. Or after sob and ---
> tag in the patch, that way it is skipped while applying..

FWIW, in drm we prefer the changelog is included in the commit message. It gives
credit to the reviewers, sometimes explains why decisions were made, and commit
message space is cheap :-).

Sean

> 
> > +#define SN_ENABLE_VID_STREAM_BIT	BIT(3)
> > +#define SN_DSIA_NUM_LANES_BITS		(BIT(4) | BIT(3))
> > +#define SN_DP_NUM_LANES_BITS		(BIT(5) | BIT(4))
> > +#define SN_DP_DATA_RATE_BITS		(BIT(7) | BIT(6) | BIT(5))
> 
> GENMASK(7, 5)
> 
> > +static int __maybe_unused ti_sn_bridge_resume(struct device *dev)
> > +{
> > +	struct ti_sn_bridge *pdata = dev_get_drvdata(dev);
> > +	int ret = 0;
> 
> superfluous initialization
> 
> > +static int __maybe_unused ti_sn_bridge_suspend(struct device *dev)
> > +{
> > +	struct ti_sn_bridge *pdata = dev_get_drvdata(dev);
> > +	int ret = 0;
> 
> here as well
> 
> > +static int ti_sn_bridge_connector_get_modes(struct drm_connector *connector)
> > +{
> > +	struct ti_sn_bridge *pdata = connector_to_ti_sn_bridge(connector);
> > +	struct edid *edid;
> > +	u32 num_modes;
> > +
> > +	if (pdata->panel) {
> > +		DRM_DEBUG_KMS("get mode from connected drm_panel\n");
> > +		return drm_panel_get_modes(pdata->panel);
> > +	}
> > +
> > +	if (!pdata->ddc)
> > +		return 0;
> > +
> > +	pm_runtime_get_sync(pdata->dev);
> 
> you should check return of this
> 
> > +static void ti_sn_bridge_set_refclk(struct ti_sn_bridge *pdata)
> > +{
> > +	int i = 0;
> 
> superfluous initialization
> 
> > +static void ti_sn_bridge_enable(struct drm_bridge *bridge)
> > +{
> > +	struct ti_sn_bridge *pdata = bridge_to_ti_sn_bridge(bridge);
> > +	unsigned int val = 0;
> 
> here as well
> 
> > +static void ti_sn_bridge_pre_enable(struct drm_bridge *bridge)
> > +{
> > +	struct ti_sn_bridge *pdata = bridge_to_ti_sn_bridge(bridge);
> > +
> > +	pm_runtime_get_sync(pdata->dev);
> 
> error check required
> -- 
> ~Vinod

-- 
Sean Paul, Software Engineer, Google / Chromium OS
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-06-05 22:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05  5:40 [PATCH v8 0/4] Add suppport for sn65dsi86 bridge chip and Innolux 2k edp panel Sandeep Panda
     [not found] ` <1528177218-1051-1-git-send-email-spanda-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-06-05  5:40   ` Sandeep Panda
2018-06-05  5:40   ` [PATCH v8 1/4] drm/bridge: add support for sn65dsi86 bridge driver Sandeep Panda
2018-06-05 11:17     ` Vinod
2018-06-05 22:32       ` Sean Paul [this message]
2018-06-05 22:59     ` Sean Paul
2018-06-13 11:05       ` spanda-sgV2jX0FEOL9JmXXK+q4OQ
     [not found]     ` <1528177218-1051-3-git-send-email-spanda-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-06-11 23:35       ` Stephen Boyd
     [not found]         ` <152876014663.16708.2127612105617872452-n1Xw8LXHxjTHt/MElyovVYaSKrA+ACpX0E9HWUfgJXw@public.gmane.org>
2018-06-13 11:06           ` spanda-sgV2jX0FEOL9JmXXK+q4OQ
2018-06-05  5:40   ` [PATCH v8 2/4] dt-bindings: drm/bridge: Document sn65dsi86 bridge bindings Sandeep Panda
     [not found]     ` <1528177218-1051-4-git-send-email-spanda-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-06-05 15:20       ` Rob Herring
2018-06-06  4:50         ` spanda-sgV2jX0FEOL9JmXXK+q4OQ
     [not found]           ` <75aab08baeecd381f573603a253dbbf1-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-06-12  8:31             ` Stephen Boyd
     [not found]               ` <152879229054.16708.14050561301794900607-n1Xw8LXHxjTHt/MElyovVYaSKrA+ACpX0E9HWUfgJXw@public.gmane.org>
2018-06-13 11:07                 ` spanda-sgV2jX0FEOL9JmXXK+q4OQ
2018-06-12  8:20         ` Stephen Boyd
2018-06-13 11:08         ` spanda-sgV2jX0FEOL9JmXXK+q4OQ
2018-06-05  5:40   ` [PATCH v8 3/4] drm/panel: add Innolux TV123WAM panel driver support Sandeep Panda
     [not found]     ` <1528177218-1051-5-git-send-email-spanda-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-06-05 22:14       ` Sean Paul
2018-06-05  5:40   ` [PATCH v8 4/4] dt-bindings: drm/panel: Document Innolux TV123WAM panel bindings Sandeep Panda

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=20180605223247.GB3373@art_vandelay \
    --to=seanpaul@chromium.org \
    --cc=abhinavk@codeaurora.org \
    --cc=chandanu@codeaurora.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=hoegsberg@chromium.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=ryadav@codeaurora.org \
    --cc=spanda@codeaurora.org \
    --cc=vkoul@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox