>
> 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
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.
>>
>>
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-by: Stephane
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 initialization and
pinctrl
> 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
On Wed, May 6, 2015 at 9:25 AM, Stephane Viau sv...@codeaurora.org
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 03/25/2015 06:49 PM, Stephane Viau wrote:
>> Add the GDSC instances that exist as part of apq8084 MMCC block.
>>
>> Signed-off-by: Stephane Viau
>> ---
>> drivers/clk/qcom/Kconfig | 1 +
>> drivers/clk/qcom/mmcc-apq8084.c | 56
>
On 03/25/2015 06:49 PM, Stephane Viau wrote:
Add the GDSC instances that exist as part of apq8084 MMCC block.
Signed-off-by: Stephane Viau sv...@codeaurora.org
---
drivers/clk/qcom/Kconfig | 1 +
drivers/clk/qcom/mmcc-apq8084.c | 56
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
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 pipeline
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
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
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/msm driver
Hi Daniel,
On Fri, Feb 20, 2015 at 3:42 PM, Beeresh Gopal gbeer...@codeaurora.org
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
> 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
>>
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
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.
> ..
>>
Hi,
Hi Stephane,
On Mon, Jul 7, 2014 at 8:04 PM, Stephane Viau sv...@codeaurora.org
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.
..
18 matches
Mail list logo
