Re: [PATCH v9 2/3] drm: bridge: Add support for Cadence MHDP8546 DPI/DP bridge

2020-09-04 Thread Tomi Valkeinen
Hi, On 04/09/2020 05:29, Laurent Pinchart wrote: >> Laurent mentioned that atomic_check should not change state. Note that >> cdns_mhdp_validate_mode_params also changes state, as it calculates tu_size, >> vs and line_thresh. > > .atomic_check() isn't allowed to change any global state, which

RE: [PATCH v9 2/3] drm: bridge: Add support for Cadence MHDP8546 DPI/DP bridge

2020-09-04 Thread Milind Parab
r...@baylibre.com; jo...@kwiboo.se; >jernej.skra...@siol.net; dri-devel@lists.freedesktop.org; >devicet...@vger.kernel.org; linux-ker...@vger.kernel.org >Cc: Yuti Suresh Amonkar ; jsa...@ti.com; >nsek...@ti.com; prane...@ti.com; nikhil...@ti.com >Subject: Re: [PATCH v9 2/3] drm: bridge: A

Re: [PATCH v9 2/3] drm: bridge: Add support for Cadence MHDP8546 DPI/DP bridge

2020-09-03 Thread Laurent Pinchart
Hi Tomi, On Tue, Sep 01, 2020 at 10:46:03AM +0300, Tomi Valkeinen wrote: > Hi Swapnil, > > On 31/08/2020 11:23, Swapnil Jakhade wrote: > > > +static int cdns_mhdp_validate_mode_params(struct cdns_mhdp_device *mhdp, > > + const struct drm_display_mode *mode, >

Re: [PATCH v9 2/3] drm: bridge: Add support for Cadence MHDP8546 DPI/DP bridge

2020-09-03 Thread Tomi Valkeinen
Hi Milind, On 03/09/2020 09:22, Milind Parab wrote: > Also, note that CDNS MHDP implements DP_FRAMER_TU_p where bits 5:0 is > tu_valid_symbols. So max programmable value is 63. > Register document gives following explanation > "Number of valid symbols per Transfer Unit (TU). Rounded down to

RE: [PATCH v9 2/3] drm: bridge: Add support for Cadence MHDP8546 DPI/DP bridge

2020-09-03 Thread Milind Parab
m; jo...@kwiboo.se; >jernej.skra...@siol.net; dri-devel@lists.freedesktop.org; >devicet...@vger.kernel.org; linux-ker...@vger.kernel.org >Cc: Milind Parab ; Yuti Suresh Amonkar >; jsa...@ti.com; nsek...@ti.com; >prane...@ti.com; nikhil...@ti.com >Subject: Re: [PATCH v9 2/3] drm: bridge: A

Re: [PATCH v9 2/3] drm: bridge: Add support for Cadence MHDP8546 DPI/DP bridge

2020-09-01 Thread Tomi Valkeinen
Hi Swapnil, On 31/08/2020 11:23, Swapnil Jakhade wrote: > + line_thresh1 = ((vs + 1) << 5) * 8 / bpp; > + line_thresh2 = (pxlclock << 5) / 1000 / rate * (vs + 1) - (1 << 5); > + line_thresh = line_thresh1 - line_thresh2 / mhdp->link.num_lanes; > + line_thresh = (line_thresh >> 5)

Re: [PATCH v9 2/3] drm: bridge: Add support for Cadence MHDP8546 DPI/DP bridge

2020-09-01 Thread Tomi Valkeinen
On 01/09/2020 10:46, Tomi Valkeinen wrote: > I think the above suggests that the driver is not properly updating all the > registers based on the > new mode and link. I tried adding cdns_mhdp_validate_mode_params() call to > cdns_mhdp_atomic_enable(), so that tu-size etc will be calculated, but

Re: [PATCH v9 2/3] drm: bridge: Add support for Cadence MHDP8546 DPI/DP bridge

2020-09-01 Thread Tomi Valkeinen
Hi Swapnil, On 31/08/2020 11:23, Swapnil Jakhade wrote: > +static int cdns_mhdp_validate_mode_params(struct cdns_mhdp_device *mhdp, > + const struct drm_display_mode *mode, > + struct drm_bridge_state *bridge_state) > +{

Re: [PATCH v9 2/3] drm: bridge: Add support for Cadence MHDP8546 DPI/DP bridge

2020-08-31 Thread Laurent Pinchart
Hi Swapnil, Thank you for the patch. On Mon, Aug 31, 2020 at 10:23:34AM +0200, Swapnil Jakhade wrote: > Add a new DRM bridge driver for Cadence MHDP8546 DPTX IP used in TI J721E > SoC. MHDP DPTX IP is the component that complies with VESA DisplayPort (DP) > and embedded Display Port (eDP)

Re: [PATCH v9 2/3] drm: bridge: Add support for Cadence MHDP8546 DPI/DP bridge

2020-08-31 Thread kernel test robot
Hi Swapnil, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on robh/for-next] [also build test WARNING on linus/master v5.9-rc3 next-20200828] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use

Re: [PATCH v9 2/3] drm: bridge: Add support for Cadence MHDP8546 DPI/DP bridge

2020-08-31 Thread kernel test robot
Hi Swapnil, Thank you for the patch! Yet something to improve: [auto build test ERROR on robh/for-next] [also build test ERROR on linus/master v5.9-rc3 next-20200828] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as