[PATCH v2] drm/msm/hdmi: Use pinctrl in HDMI driver

> > On Tue, 2015-06-02 at 10:12 -0500, "Stéphane Viau" wrote: >> Hi Ivan, >> >> > Hi Stephane, >> > >> > On Mon, 2015-06-01 at 16:28 -0400, Stephane Viau wrote: >> > > Some targets (eg: msm8994) use the pinctrl framework to configure >> > > interface pins. This change adds support for initializa

[PATCH v2] drm/msm/hdmi: Use pinctrl in HDMI driver

Hi Ivan, > > Hi Stephane, > > On Mon, 2015-06-01 at 16:28 -0400, Stephane Viau wrote: >> Some targets (eg: msm8994) use the pinctrl framework to configure >> interface pins. This change adds support for initialization and >> pinctrl active/sleep state control for the HDMI driver. >> >> Signed-off-

[PATCH] drm/msm/mdp4: Support NV12MT format in mdp4

Hi Rob, > Using fb modifier flag, support NV12MT format in MDP4. > > v2: > - rework the modifier's description [Daniel Vetter's comment] > - drop .set_mode_config() callback [Rob Clark's comment] > v3: > - change VENDOR's name and restrict usage to NV12 [pointed by Daniel] > > Signed-off-by: Rob C

[PATCH] drm/msm: Fix compil issue when DRM_MSM_FBDEV is disabled

> On Wed, May 6, 2015 at 9:25 AM, Stephane Viau > wrote: >> When CONFIG_DRM_MSM_FBDEV is not defined, >> CONFIG_DRM_KMS_FB_HELPER does not get selected and >> drm_fb_helper_*() helper functions are thus not available. >> >> This change fixes these link issues. > > Hmm, didn't Archit start on maki

[PATCH v3 3/4] drm/msm/mdp5: Add START signal to kick off certain pipelines

Hi Archit, > Hi Stephane, > > On 03/14/2015 01:19 AM, Stephane Viau wrote: >> Some interfaces (WB, DSI Command Mode) need to be kicked off >> through a START Signal. This signal needs to be sent at the right >> time and requests in some cases to keep track of the pipeline >> status (eg: whether pi

[PATCH 5/5] drm/msm/mdp5: Add hardware configuration for msm8x16

Hi, > Hi, > > On 03/09/2015 06:41 PM, Stephane Viau wrote: >> This change adds the hw configuration for msm8x16 chipsets in >> mdp5_cfg module. >> >> Note that only one external display interface is present in this >> configuration (DSI) but has not been enabled yet. It will be enabled >> once drm

[PATCH 2/2] drm/msm: Support NV12MT format in mdp4

Hi Daniel, > On Fri, Feb 20, 2015 at 3:42 PM, Beeresh Gopal > wrote: >> +/* Samsung framebuffer modifiers */ >> + >> +/* >> + * NV12 64x32 Tiled >> + * >> + * 2 planes Y and CbCr, grouped into 64x32 macro tiles, >> + * with a non-standard order in memory (Z-shape). >> + * >> + * Pixel layout iden

[PATCH 4/4] drm/msm/mdp5: Make the intf connection in config module

> Hi, Hi Archit, > > On 03/04/2015 12:06 AM, Stephane Viau wrote: >> Up until now, we assume that eDP is tight to intf_0 and HDMI to >> intf_3. This information shall actually come from the mdp5_cfg >> module since it can change from one chip to another. >> >> Signed-off-by: Stephane Viau >> ---

[PATCH 1/7] drm: add atomic fxns

Hi, >> { >> int ret = -EINVAL; >> -struct drm_connector *connector = obj_to_connector(obj); >> >> /* Do DPMS ourselves */ >> if (property == connector->dev->mode_config.dpms_property) { >> if (connector->funcs->dpms) >> (*connector->funcs->dpms

[PATCH] drm/msm/mdp5: add support for MDP5 v1.3

Hi, > Hi Stephane, > > On Mon, Jul 7, 2014 at 8:04 PM, Stephane Viau > wrote: >> >> MDP5 has several functional blocks (ie: VIG/RGB pipes, LMs, ...). >> From one revision to another, these blocks' base addresses might >> change due to the number of instances present in the MDP5 hw. > .. >> -stati