dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: bivvy.bi@rock-chips.com, jernej.skrabec@siol.net,
	xzy.xu@rock-chips.com, kuninori.morimoto.gx@renesas.com,
	jonas@kwiboo.se, sean@poorly.run, briannorris@chromium.org,
	dianders@chromium.org,
	DRI Development <dri-devel@lists.freedesktop.org>,
	philippe.cornu@st.com, yannick.fertre@st.com,
	nickey.yang@rock-chips.com, eddie.cai@rock-chips.com,
	Laurent.pinchart@ideasonboard.com, sam@ravnborg.org
Subject: Re: [PATCH v3] drm/bridge/synopsys: dsi: driver-specific configuration of phy timings
Date: Mon, 25 Nov 2019 10:32:12 +0100	[thread overview]
Message-ID: <3580716.ThYBqbcnhK@diego> (raw)
In-Reply-To: <b8c43767-d065-d6da-a588-9a05e8aa4f1e@baylibre.com>

Am Montag, 25. November 2019, 10:28:12 CET schrieb Neil Armstrong:
> Hi,
> 
> On 23/11/2019 21:51, Heiko Stuebner wrote:
> > Hi Neil,
> > 
> > Am Samstag, 23. November 2019, 13:38:41 CET schrieb Neil Armstrong:
> >> Le 23/11/2019 à 11:39, Heiko Stuebner a écrit :
> >>> From: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
> >>>
> >>> The timing values for dw-dsi are often dependent on the used display and
> >>> according to Philippe Cornu will most likely also depend on the used phy
> >>> technology in the soc-specific implementation.
> >>>
> >>> To solve this and allow specific implementations to define them as needed
> >>> add a new get_timing callback to phy_ops and call this from the dphy_timing
> >>> function to retrieve the necessary values for the specific mode.
> >>>
> >>> Right now this handles the hs2lp + lp2hs where Rockchip SoCs need handling
> >>> according to the phy speed, while STM seems to be ok with static values.
> >>>
> >>> changes in v3:
> >>> - check existence of phy_ops->get_timing in __dw_mipi_dsi_probe()
> >>> - emit actual error when get_timing() call fails
> >>> - add tags from Philippe and Yannick
> >>>
> >>> changes in v2:
> >>> - add driver-specific handling, don't force all bridge users to use
> >>>   the same timings, as suggested by Philippe
> >>>
> >>> Suggested-by: Philippe Cornu <philippe.cornu@st.com>
> >>> Signed-off-by: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
> >>> Reviewed-by: Philippe Cornu <philippe.cornu@st.com>
> >>> Tested-by: Yannick Fertre <yannick.fertre@st.com>
> 
> 
> You forgot to Cc dri-devel, so I can't apply it.

oh dang ... resend coming shortly

Heiko

> 
> Could you resent it ?
> 
> Neil
> 
> >>> ---
> >>>  drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.c | 27 +++++--
> >>>  drivers/gpu/drm/rockchip/Kconfig              |  1 +
> >>>  .../gpu/drm/rockchip/dw-mipi-dsi-rockchip.c   | 78 +++++++++++++++++++
> >>>  drivers/gpu/drm/stm/dw_mipi_dsi-stm.c         | 13 ++++
> >>>  include/drm/bridge/dw_mipi_dsi.h              |  9 +++
> >>>  5 files changed, 121 insertions(+), 7 deletions(-)
> >>>
> >> [...]
> >>
> >>
> >> Looks good,
> >> Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
> >>
> >> I can apply it on monday if you want.
> > 
> > that would be very cool. Looking forward to monday then
> > 
> > Thanks
> > Heiko
> > 
> > 
> > 
> 
> 




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

      reply	other threads:[~2019-11-25  9:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191123103904.22843-1-heiko@sntech.de>
     [not found] ` <45168bb1-ca49-3a88-12d6-f398bebac27f@baylibre.com>
     [not found]   ` <5060226.21S8zkcLb9@phil>
2019-11-25  9:28     ` [PATCH v3] drm/bridge/synopsys: dsi: driver-specific configuration of phy timings Neil Armstrong
2019-11-25  9:32       ` Heiko Stübner [this message]

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=3580716.ThYBqbcnhK@diego \
    --to=heiko@sntech.de \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=bivvy.bi@rock-chips.com \
    --cc=briannorris@chromium.org \
    --cc=dianders@chromium.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eddie.cai@rock-chips.com \
    --cc=jernej.skrabec@siol.net \
    --cc=jonas@kwiboo.se \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=narmstrong@baylibre.com \
    --cc=nickey.yang@rock-chips.com \
    --cc=philippe.cornu@st.com \
    --cc=sam@ravnborg.org \
    --cc=sean@poorly.run \
    --cc=xzy.xu@rock-chips.com \
    --cc=yannick.fertre@st.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox