ursor_updates flag.
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.c | 33 ++---
drivers/gpu/drm/msm/msm_atomic.c| 5 -
2 files changed, 26 insertions(+), 12 deletions(-)
diff --git a/drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.c
b/dr
.
This is borrowed from downstream MDP5 kernel driver. Without this, we
don't see any cursor plane content.
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/msm/mdp/mdp5/mdp5_crtc.c | 30 ++
1 file changed, 30 insertions(+)
diff --git a/drivers/gpu/drm/msm/mdp/m
, but crtc_state would need to be derived differently.
Refactor mdp5_plane_atomic_check to mdp5_plane_atomic_check_with_state
such that the latter takes crtc_state as an argument.
This is similar to what the intel driver has done for async cursor
updates.
Signed-off-by: Archit Taneja
---
drivers/gpu/dr
ery new fb. This in turn should ensure that
the fb is pinned/prepared.
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/msm/mdp/mdp5/mdp5_crtc.c | 7 ++
drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.h | 1 +
drivers/gpu/drm/msm/mdp/mdp5/mdp5_plane.c | 110 +-
3 files ch
On 01/17/2017 01:58 PM, Laurent Pinchart wrote:
Hello,
This patch series contains the part of my pending dw-hdmi patches that have
been successfully tested on all three supported platforms (i.MX6, RK3288 and
R-Car H3) and have been reviewed without any problem being reported.
All patches here
avoid race, as
suggested by Laurent
* Reworked the __adv7511_power_on helpers to avoid calling
regcache_sync in the EDID probe path
* Added new patch to set EDID_I2C_ADDR register before doing
EDID read.
Cc: David Airlie
Cc: Archit Taneja
Cc: Wolfram Sang
Cc: Lars-Peter Clausen
Cc: La
On 01/20/2017 01:47 AM, Stephen Boyd wrote:
On 01/07, Archit Taneja wrote:
+
+static struct clk *pll_14nm_postdiv_register(struct dsi_pll_14nm *pll_14nm,
+const char *name,
+const char *parent_name
On 01/20/2017 01:08 PM, Andrzej Hajda wrote:
Burst transmissions are used in MHL3 mode negotiation.
Signed-off-by: Andrzej Hajda
---
drivers/gpu/drm/bridge/sil-sii8620.c | 196 ++-
drivers/gpu/drm/bridge/sil-sii8620.h | 4 +
2 files changed, 198 insertions(+
On 01/20/2017 01:08 PM, Andrzej Hajda wrote:
Due to asynchronous nature of MHL flow of execution is dispersed. Logical
continuation of some actions happens after response of peer, i.e in interrupt
handler. To simplify coding continuation mechanism has been added - it is now
possible to provide
On 01/20/2017 01:08 PM, Andrzej Hajda wrote:
MHL3 protocol requires registry adjustments depending on chosen video mode.
Necessary information is gathered in mode_fixup callback. In case of HDMI
video modes driver should also send special AVI and MHL infoframes.
Signed-off-by: Andrzej Hajda
-
Hi,
On 01/23/2017 10:58 PM, Javier Martinez Canillas wrote:
Hello Archit,
On 01/09/2017 06:47 AM, Archit Taneja wrote:
On 01/05/2017 01:01 PM, Sean Paul wrote:
On Fri, Dec 30, 2016 at 4:57 AM, Marek Szyprowski
wrote:
Analogix_dp_bind() can be called from component framework, which
On 01/23/2017 05:50 PM, Arnd Bergmann wrote:
The of_node member in struct drm_bridge is hidden when CONFIG_OF
is disabled, causing a build error:
drivers/gpu/drm/bridge/dw-hdmi.c: In function '__dw_hdmi_probe':
drivers/gpu/drm/bridge/dw-hdmi.c:2063:14: error: 'struct drm_bridge' has no
member
gpio_free warning removal patch to improve
indentation
Changes in v2:
- Use the recently created drm_connector_register_all and
drm_connector_unregister_all helpers instead of writing it ourselves
Archit Taneja (3):
drm/msm/hdmi: Prevent gpio_free related kernel warnings
drm/msm
Calling the legacy gpio_free on an invalid GPIO (a GPIO numbered -1)
results in kernel warnings. This causes a lot of backtraces when
we try to unload the drm/msm module.
Call gpio_free only on valid GPIOs.
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/msm/hdmi/hdmi_connector.c | 9
ad of
devm_kzalloc to ensure that that the connectors can be successfully
unregistered when the msm driver module is removed. The memory for the
connectors is unallocated when drm_mode_config_cleanup() is called
during either during an error or during driver remove.
Signed-off-by: Archit Taneja
---
driver
odule insertions/removals.
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/msm/msm_drv.c | 125 --
1 file changed, 71 insertions(+), 54 deletions(-)
diff --git a/drivers/gpu/drm/msm/msm_drv.c b/drivers/gpu/drm/msm/msm_drv.c
index 8c5b257..a6db6e6 100644
On 05/03/2016 07:22 AM, Xinliang Liu wrote:
> On 9 March 2016 at 18:57, Archit Taneja wrote:
>> ADV7533 is a DSI to HDMI encoder chip. It's like ADV7511, but with an
>> additional DSI RX block that takes in DSI video mode output.
>>
>> Trying to get this drive
Hi Laurent,
On 04/22/2016 10:40 AM, Archit Taneja wrote:
> Hi Laurent,
>
>
> On 04/22/2016 03:59 AM, Laurent Pinchart wrote:
>> Hi Archit,
>>
>> Thank you for the patch.
>>
>> On Wednesday 09 Mar 2016 16:27:15 Archit Taneja wrote:
>>> In order
e we know what's the
right way to link the gpu and display nodes together (if needed at
all) we can add the required binding.
The rest of the changes are minor cleanups and fixes to prepare the
driver and binding documents before we really start adding the display
nodes.
Archit Taneja (9):
d
I, HDMI in MDSS. These are also the subcomponent
devices that we need add. This description of ports complies with the
generic graph bindings.
In MDP4, the LVDS port's output connects directly to the LVDS panel. In
this case, we don't try to add it as a component.
Signed-off-by: Archit
now how to link the kms and gpu drivers, we'll drop this method
and use the correct binding.
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/msm/msm_drv.c | 26 +++---
1 file changed, 19 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/msm/msm_drv.c b/drivers/g
The LCDC port is the first in the list of the output ports in MDP4.
Mention this explicitly in the driver.
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/msm/mdp/mdp4/mdp4_kms.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/msm/mdp/mdp4/mdp4_kms.c
MDP.
The GPU phandle is removed too until we figure out what's the right way
to specify it in DT.
Signed-off-by: Archit Taneja
---
.../devicetree/bindings/display/msm/mdp.txt| 75 --
1 file changed, 71 insertions(+), 4 deletions(-)
diff --git a/Documentation/devi
Some cleanups:
- Use simpler names for DT nodes in the example
- Fix phandle for specifying data lane mapping in the example.
- Use references instead of dumping Document links everywhere
Signed-off-by: Archit Taneja
---
.../devicetree/bindings/display/msm/dsi.txt| 23
:
- - ---
| MDP | --> | DSI | --> | Panel |
- - ---
(Port 0) (Port 1)
Until now, there was only one Port representing the output. Update the
DSI host driver such that it parses Port #1 for a connected device.
Signed-off-by: Archit
The DSI host links to the DSI PHY device using a custom binding. Switch to
the generic PHY bindings. The DSI PHY driver itself doesn't use the common
PHY framework for now.
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/msm/dsi/dsi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
: Archit Taneja
---
.../devicetree/bindings/display/msm/dsi.txt| 53 +++---
1 file changed, 37 insertions(+), 16 deletions(-)
diff --git a/Documentation/devicetree/bindings/display/msm/dsi.txt
b/Documentation/devicetree/bindings/display/msm/dsi.txt
index bf41d7c..0223f06
to set up the MMCC RCGs that feed to
the DSI host. Use the DSI PHY provided clocks to set up the parents
of these assigned clocks.
Signed-off-by: Archit Taneja
---
Documentation/devicetree/bindings/display/msm/dsi.txt | 15 +++
1 file changed, 15 insertions(+)
diff --git a
On 05/03/2016 06:12 PM, Rob Herring wrote:
> On Tue, May 3, 2016 at 5:57 AM, Archit Taneja
> wrote:
>> The driver currently identifies the GPU components it needs by parsing
>> a phandle list from the 'gpus' DT property.
>>
>> This isn't the right
On 05/03/2016 07:32 PM, Philipp Zabel wrote:
> Am Dienstag, den 03.05.2016, 16:28 +0530 schrieb Archit Taneja:
>> The DSI node now has two ports that describe the connection between the
>> MDP interface output and the DSI input, and the connection between the DSI
>> out
On 05/03/2016 07:35 PM, Philipp Zabel wrote:
> Am Dienstag, den 03.05.2016, 16:27 +0530 schrieb Archit Taneja:
>> Some cleanups:
>>
>> - Use simpler names for DT nodes in the example
>> - Fix phandle for specifying data lane mapping in the example.
>> - Use refer
On 5/4/2016 7:08 PM, Rob Herring wrote:
> On Tue, May 03, 2016 at 04:27:56PM +0530, Archit Taneja wrote:
>> The MDP DT node now contains a list of ports that describe how it connects
>> to external encoder interfaces like DSI and HDMI. These follow the
>> standard of_graph b
On 5/4/2016 7:14 PM, Rob Herring wrote:
> On Tue, May 03, 2016 at 04:28:01PM +0530, Archit Taneja wrote:
>> The PLL in the DSI PHY block generates 2 clock outputs (Byte and Pixel
>> clocks) that are fed into the Multimedia Clock Controller (MMCC). The MMCC
>> uses these as s
On 05/10/2016 02:08 AM, Laurent Pinchart wrote:
> Hi Archit,
>
> On Tuesday 03 May 2016 12:27:38 Archit Taneja wrote:
>> On 04/22/2016 10:40 AM, Archit Taneja wrote:
>>> On 04/22/2016 03:59 AM, Laurent Pinchart wrote:
>>>> On Wednesday 09 Mar 2016 16:27:15 Ar
op.org/archives/dri-devel/2015-July/087088.html
Archit Taneja (7):
drm/i2c: adv7511: Convert to drm_bridge
drm/i2c: adv7511: Fix mutex deadlock when interrupts are disabled
drm/i2c: adv7511: Initial support for ADV7533
drm/i2c: adv7533: Create a MIPI DSI device
drm/i2c: adv7533: Use
nector ops.
The driver now creates its own connector when a kms driver attaches
itself to the bridge. Therefore, kms drivers don't need to create
their own connectors anymore.
The old encoder slave ops are now used by the new bridge and connector
entities.
Signed-off-by: Archit Taneja
---
mutex again)
In adv7511_irq_process, don't call drm_helper_hpd_irq_event when not
called from the interrupt handler. It doesn't serve any purpose there
anyway.
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/i2c/adv7511.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff -
enables ADV7533 support. Use DT compatible
strings to populate the ADV7533 type enum. Add minimal register
configurations belonging to the DSI/CEC register map. Keep the ADV7533
code in a separate file.
Originally worked on by Lars-Peter Clausen
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/i2c
parameters (number of data lanes for now) that are required
for DSI RX to work correctly. Hardcode few other parameters (rgb,
embedded_sync) for now.
Select DRM_MIPI_DSI config option only when ADV7533 support is enabled.
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/i2c/Kconfig | 1 +
drivers
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/i2c/adv7511.c | 2 ++
drivers/gpu/drm/i2c/adv7511.h | 3 +++
drivers/gpu/drm/i2c/adv7533.c | 60 +--
3 files changed, 63 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i2c/adv7511.c b/driv
Lower modes on ADV7533 require lower number of DSI lanes for correct
operation. If ADV7533 is being used with 4 DSI lanes, then switch the
lanes to 3 when the target mode's pixel clock is less than 80 Mhz.
Based on patch by Andy Green
Signed-off-by: Archit Taneja
---
drivers/gpu/dr
Add description of ADV7533. Add the required and optional properties that
are specific to it.
Cc: devicetree at vger.kernel.org
Acked-by: Rob Herring
Signed-off-by: Archit Taneja
---
.../bindings/display/bridge/adi,adv7511.txt| 26 +-
1 file changed, 21 insertions
On 05/16/2016 05:31 PM, Laurent Pinchart wrote:
> Hi Archit,
>
> On Friday 22 Apr 2016 11:10:18 Archit Taneja wrote:
>> On 04/22/2016 04:02 AM, Laurent Pinchart wrote:
>>> On Wednesday 09 Mar 2016 16:27:18 Archit Taneja wrote:
>>>> Add description of AD
On 05/17/2016 09:48 AM, Xinliang Liu wrote:
> On 17 May 2016 at 11:43, Archit Taneja wrote:
>>
>>
>> On 05/16/2016 05:31 PM, Laurent Pinchart wrote:
>>>
>>> Hi Archit,
>>>
>>> On Friday 22 Apr 2016 11:10:18 Archit Taneja wrote:
ution to this issue isn't a part of the
RFC yet.
We're looking for feedback here and wondering whether this is the right
way to go or not.
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/drm_atomic.c | 9 +
drivers/gpu/drm/drm_crtc.c | 38 +++
On 05/25/2016 12:40 PM, Daniel Vetter wrote:
> On Wed, May 25, 2016 at 12:03:39PM +0530, Archit Taneja wrote:
>> High resoultion modes (4K/5K) are supported by encoder/crtc hardware, but
>> the backing hardware planes to scanout these buffers generally don't
>> support
On 05/25/2016 10:06 PM, Rob Clark wrote:
> On Wed, May 25, 2016 at 9:12 AM, Daniel Vetter wrote:
>> On Wed, May 25, 2016 at 04:28:36PM +0530, Archit Taneja wrote:
>>> On 05/25/2016 12:40 PM, Daniel Vetter wrote:
>>>> - Is the size/width really independent
On 02/22/2016 08:23 AM, Rob Herring wrote:
> On Mon, Feb 15, 2016 at 06:30:59PM +0530, Archit Taneja wrote:
>> The DSI driver is currently unaware of how the DSI clock and data pins
>> are mapped to the logical lanes provided by the DSI controller.
>>
>> Use the
On 02/22/2016 08:24 AM, Rob Herring wrote:
> On Mon, Feb 15, 2016 at 12:23:26PM +0530, Archit Taneja wrote:
>> Add HDMI PHY bindings. Update the example to use HDMI PHY.
>>
>> Add a missing power-domains property in the HDMI core bindings.
>>
>> Cc: devicet
On 02/23/2016 12:57 AM, Rob Herring wrote:
> On Mon, Feb 22, 2016 at 5:07 AM, Archit Taneja
> wrote:
>>
>>
>> On 02/22/2016 08:24 AM, Rob Herring wrote:
>>>
>>> On Mon, Feb 15, 2016 at 12:23:26PM +0530, Archit Taneja wrote:
>>>>
>>
On 02/23/2016 02:48 PM, Tomi Valkeinen wrote:
>
> On 22/02/16 22:10, Rob Herring wrote:
>
>>> If we want all DSI host controllers to use a common binding to describe
>>> lanes, we'd need to go with the most flexible one, and the driver
>>> restricts it to the subsets that we support.
>
> True, bu
On 02/24/2016 01:34 AM, Rob Herring wrote:
> On Tue, Feb 23, 2016 at 01:11:24PM +0200, Tomi Valkeinen wrote:
>>
>>
>> On 23/02/16 12:43, Archit Taneja wrote:
>>>
>>>
>>> On 02/23/2016 02:48 PM, Tomi Valkeinen wrote:
>>>>
>>>&
Hi Kishon,
On 02/24/2016 05:30 PM, Kishon Vijay Abraham I wrote:
> Hi Archit,
>
> On Tuesday 23 February 2016 03:06 PM, Archit Taneja wrote:
>>
>>
>> On 02/23/2016 12:57 AM, Rob Herring wrote:
>>> On Mon, Feb 22, 2016 at 5:07 AM, Archit Taneja
>>>
panels that connect to the
dsi host. The downstream driver controlled it within the DSI
driver itself, which led to the confusion.
- Updated the DT bindings for parsing DSI data lanes
- Added a patch to constify iommu port names
- Fixed some checkpatch warnings.
Archit Taneja (5):
drm/msm/mdp
Assign drm_atomic_helper_crtc_set_property helper to MDP4 and MDP5
crtcs' set_property ops. This replaces the custom funcs that
returned an error even for standard crtc properties.
Signed-off-by: Archit Taneja
Reviewed-by: Daniel Vetter
---
drivers/gpu/drm/msm/mdp/mdp4/mdp4_crtc.
From: Rob Clark
Signed-off-by: Rob Clark
---
drivers/gpu/drm/msm/msm_iommu.c | 6 --
drivers/gpu/drm/msm/msm_mmu.h | 4 ++--
2 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/msm/msm_iommu.c b/drivers/gpu/drm/msm/msm_iommu.c
index 7ac2f19..a7a0b6d 100644
--- a
From: Sricharan R
attach_dev gets called in mdp4_kms_init, but there is no corresponding
detach_dev called in the error path or in the kms driver unload path.
Detach and destroy mmu in mdp4_destroy.
Signed-off-by: Sricharan R
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/msm/mdp/mdp4
We have a msm_fbev_free function to uninit fb_helper stuff, but we aren't
using it. Call it in msm_unload.
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/msm/msm_drv.c | 5 +
drivers/gpu/drm/msm/msm_drv.h | 1 +
2 files changed, 6 insertions(+)
diff --git a/drivers/gpu/drm/msm/msm_
, these are guaranteed to be different.
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/msm/dsi/dsi_host.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/gpu/drm/msm/dsi/dsi_host.c
b/drivers/gpu/drm/msm/dsi/dsi_host.c
index 48f9967..69bac59 100644
--- a/drivers/gpu/drm/msm/dsi
VDD regulator input was specified for MSM8916. It turns our that this
regulator is used for the display panels used on MSM8916 platforms, but
not the DSI controller itself. Drop this regulator from the list.
Reported-by: Vinay Simha
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/msm/dsi
n
Signed-off-by: Archit Taneja
---
.../devicetree/bindings/display/msm/dsi.txt| 32 +-
drivers/gpu/drm/msm/dsi/dsi_host.c | 116 +
2 files changed, 125 insertions(+), 23 deletions(-)
diff --git a/Documentation/devicetree/bindings/display/msm/
commit messages to point out that HDMI functionality will
break if we pull in the commits that adds the PHY driver, but not
the commit that updates PHY/PLL register offsets.
- Change the order of patches such that bisectability issues are
reduced to a minimum.
Archit Taneja (10):
drm/msm/hdmi
integrate
with the driver, as it doesn't have a HPD gpio input to them. Also, it
cleans things up a bit.
We still use the legacy gpio api here, as we might need to backport this
driver to downstream kernels.
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/msm/hdmi/hdmi.c
: Archit Taneja
---
drivers/gpu/drm/msm/hdmi/hdmi_connector.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/gpu/drm/msm/hdmi/hdmi_connector.c
b/drivers/gpu/drm/msm/hdmi/hdmi_connector.c
index deec1f9..3973d46 100644
--- a/drivers/gpu/drm/msm/hdmi/hdmi_connector.c
+++ b/drivers/gpu
The driver doesn't use the common PHY framework for now. This is because
it's hard to map our ops with the ops provided by the framework. The
bindings used for this is the generic phy bindings. So, this can be
adapted to the PHY framework in the future, if possible.
Signed-off-by
driver will use these until the HDMI PHY/PLL register offsets aren't
considered as separate domains (i.e. their offsets start from 0).
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/msm/Makefile | 1 +
drivers/gpu/drm/msm/hdmi/hdmi.h | 9 +
drivers/gpu/drm/msm
Make HDMI core get its PHY by parsing the "phys" phandle. The core will use
this PHY reference to enable/disable PHY. The driver defers probe until PHY
isn't available.
The DT bindings used here is the same as the one used for PHYs using the
common PHY framework bindings.
Signed
aren't updated to be used as
separate domains.
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/msm/hdmi/hdmi.c | 25 +-
drivers/gpu/drm/msm/hdmi/hdmi.h | 10 -
drivers/gpu/drm/msm/hdmi/hdmi_bridge.c | 8 +-
drivers/gpu/drm/msm/hdmi/hdmi_phy_8960.c
- Create separate domains for 8960 PHY and PLL
- Create separate domains for 8x60 PHY
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/msm/hdmi/hdmi.xml.h | 157 +---
1 file changed, 74 insertions(+), 83 deletions(-)
diff --git a/drivers/gpu/drm/msm/hdmi
Adds HDMI 8996 PHY offsets. The offsets are divided into 3 parts:
- Core HDMI PHY registers
- HDMI PLL registers (part of QSERDES block)
- HDMI TX lane registers (part of QSERDES block)
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/msm/hdmi/hdmi.xml.h | 500
Add support for the HDMI PHY/PLL found in MSM8996/APQ8096.
Unlike the previous PHYs supported in the driver, this doesn't need
the powerup/powerdown ops. The PLL prepare/unprepare clock ops
enable/disable the phy itself.
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/msm/Mak
Add HDMI PHY bindings. Update the example to use HDMI PHY.
Added a missing power-domains property in the HDMI core bindings. Also,
simplified HDMI TX's DT node name in the example.
Cc: devicetree at vger.kernel.org
Cc: Rob Herring
Signed-off-by: Archit Taneja
---
.../devicetree/bin
On 02/25/2016 02:09 PM, Arnd Bergmann wrote:
> On Thursday 25 February 2016 11:22:35 Archit Taneja wrote:
>> HDMI on MSM8996 has a TX block that is compatible with the older
>> versions apart from some minor changes. The HDMI PHY and PLL on MSM8996
>> are new.
>>
>&
On 02/25/2016 02:17 PM, Archit Taneja wrote:
>
>
> On 02/25/2016 02:09 PM, Arnd Bergmann wrote:
>> On Thursday 25 February 2016 11:22:35 Archit Taneja wrote:
>>> HDMI on MSM8996 has a TX block that is compatible with the older
>>> versions apart from some minor
On 02/26/2016 04:34 AM, Laurent Pinchart wrote:
> Hi Archit,
>
> Thank you for the patch, I finally got around to testing it. Sorry for the
> delay.
>
> On Saturday 09 January 2016 22:22:26 Archit Taneja wrote:
>> The hdmi output in rcar-du uses the i2c slave encoder int
Hi,
I had some minor comments. Sorry about sharing this late. Otherwise,
the looks good to me.
On 02/26/2016 02:10 PM, Xinliang Liu wrote:
> Add kirin DRM master driver for hi6220 SoC which used in HiKey board.
> Add dumb buffer feature.
> Add prime dmabuf feature.
>
> v6: None.
> v5: None.
> v4:
RL);
> + /* dsi pixel on */
> + writel(DSI_PCLK_ON, base + LDI_HDMI_DSI_GT);
> +}
> +
> +static void ade_crtc_enable(struct drm_crtc *crtc)
> +{
> + struct ade_crtc *acrtc = to_ade_crtc(crtc);
> + struct ade_hw_ctx *ctx = acrtc->ctx;
> + int ret;
>
On 2/26/2016 2:10 PM, Xinliang Liu wrote:
> Add plane funcs and helper funcs for ADE.
>
> v6: None.
> v5: None.
> v4: None.
> v3:
> - A few cleanup.
> v2:
> - Remove abtraction layer.
>
> Signed-off-by: Xinliang Liu
> ---
> drivers/gpu/drm/hisilicon/kirin/kirin_drm_ade.c | 535
> +
On 2/26/2016 2:10 PM, Xinliang Liu wrote:
> Add vblank irq handle.
>
> v6: None.
> v5: None.
> v4: None.
> v3:
> - Remove hisi_get_crtc_from_index func.
> - A few cleanup.
> v2:
> - Remove abtraction layer.
>
> Signed-off-by: Xinliang Liu
> ---
> drivers/gpu/drm/hisilicon/kirin/kirin_drm_ade.c
On 2/26/2016 2:10 PM, Xinliang Liu wrote:
> Add DesignWare MIPI DSI Host Controller v1.02 encoder driver
> for hi6220 SoC.
>
> v6:
> - Change "pclk_dsi" to "pclk".
> v5: None.
> v4: None.
> v3:
> - Rename file name to dw_drm_dsi.c
> - Make encoder type as DRM_MODE_ENCODER_DSI.
> - A few cleanup.
On 2/26/2016 2:10 PM, Xinliang Liu wrote:
> Add DesignWare dsi host driver for hi6220 SoC.
>
> v6: None.
> v5: None.
> v4: None.
> v3: None.
> v2:
> - Remove abtraction layer.
Reviewed-by: Archit Taneja
>
> Signed-off-by: Xinliang Liu
> ---
> drivers/
On 2/26/2016 2:10 PM, Xinliang Liu wrote:
> Add support for external HDMI bridge.
>
> v6: None.
> v5: None.
> v4: None.
> v3:
> - Fix a typo: s/exteranl/external.
> v2:
> - Remove abtraction layer.
>
Reviewed-by: Archit Taneja
> Signed-off-by: Xinliang Liu
&g
t flags,
> they are cleared in POWER_DOWN mode anyhow (according to docs and my
> tests).
I tried this on adv7533 and it works fine. The other patches look good
too.
Tested-by: Archit Taneja
Thanks,
Archit
>
> Signed-off-by: Wolfram Sang
> ---
> d
Hi Thierry,
Can you pick up these DSI patches, or would it make more sense for
these to go via someone else?
Thanks,
Archit
On 12/10/2015 06:11 PM, Archit Taneja wrote:
> We are currently restricted when it comes to supporting DSI on devices
> that have a non-DSI control bus. For exampl
On 01/06/2016 05:55 PM, Boris Brezillon wrote:
> Add basic support for the sil902x RGB -> HDMI bridge.
> This driver does not support audio output yet.
>
> Signed-off-by: Boris Brezillon
> ---
> Hello,
>
> This patch is only adding basic support for the sil9022 chip.
> As stated in the commit lo
nector ops.
The driver now creates its own connector when a kms driver attaches
itself to the bridge. Therefore, kms drivers don't need to create
their own connectors anymore.
The old encoder slave ops are now used by the new bridge and connector
entities.
Signed-off-by: Archit Taneja
---
y the bridge driver.
Compile tested only.
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/rcar-du/Makefile | 3 +-
drivers/gpu/drm/rcar-du/rcar_du_encoder.c | 3 +-
drivers/gpu/drm/rcar-du/rcar_du_encoder.h | 7 +-
drivers/gpu/drm/rcar-du/rcar_du_hdmicon.c
Hi Laurent,
On 12/3/2015 9:41 PM, Archit Taneja wrote:
>
>
> On 12/3/2015 9:25 PM, Rob Clark wrote:
>> On Thu, Dec 3, 2015 at 10:28 AM, Laurent Pinchart
>> wrote:
>>> On Thursday 03 December 2015 10:02:02 Rob Clark wrote:
>>>> On Mon, Jul 27, 2015 at
On 01/11/2016 07:38 AM, Laurent Pinchart wrote:
> Hi Archit,
>
> Thanks a lot for the patch.
>
> On Saturday 09 January 2016 22:20:25 Archit Taneja wrote:
>> We don't want to use the old i2c slave encoder interface anymore.
>
> I happily agree with that :-)
&
Hi Jitao,
On 01/13/2016 07:48 AM, Jitao Shi wrote:
> This patch adds drm_bridge driver for parade DSI to eDP bridge chip.
>
> Signed-off-by: Jitao Shi
> ---
> Changes since v6:
> - Add ps8640 firmware update function
> - Change i2c to i2c_transfer from i2c_master_recv/i2c_master_send
> - Ad
On 05/08/2015 08:00 PM, Rob Clark wrote:
> On Fri, May 8, 2015 at 9:54 AM, Daniel Vetter wrote:
>> On Fri, May 08, 2015 at 09:03:19AM -0400, Rob Clark wrote:
>>> On Fri, May 8, 2015 at 6:11 AM, Archit Taneja
>>> wrote:
>>>> Allow drm_bridge objects to
ans up the atomic and crtc helper files a bit.
Reviewed-by: Jani Nikula
Reviewed-by: Rob Clark
Signed-off-by: Archit Taneja
---
v3:
- Add headerdocs for the new functions
v2:
- Add EXPORT_SYMBOL for the new functions
- Fix logic issue in mode_fixup()
drivers/gpu/drm/drm_a
Add headerdocs for drm_bridge_add, drm_bridge_remove, drm_bridge_attach and
of_drm_find_bridge.
Signed-off-by: Archit Taneja
---
drivers/gpu/drm/drm_bridge.c | 28
1 file changed, 28 insertions(+)
diff --git a/drivers/gpu/drm/drm_bridge.c b/drivers/gpu/drm
Hi,
On 05/19/2015 03:04 PM, Daniel Vetter wrote:
> On Tue, May 19, 2015 at 02:05:04PM +0530, Archit Taneja wrote:
>> Allow drm_bridge objects to link to each other in order to form an encoder
>> chain. The requirement for creating a chain of bridges comes because the
>> MSM d
On 05/19/2015 03:07 PM, Daniel Vetter wrote:
> On Tue, May 19, 2015 at 02:05:05PM +0530, Archit Taneja wrote:
>> Add headerdocs for drm_bridge_add, drm_bridge_remove, drm_bridge_attach and
>> of_drm_find_bridge.
>>
>> Signed-off-by: Archit Taneja
>
> You also n
On 05/19/2015 09:00 PM, Daniel Vetter wrote:
> On Tue, May 19, 2015 at 04:37:44PM +0530, Archit Taneja wrote:
>> On 05/19/2015 03:04 PM, Daniel Vetter wrote:
>>> On Tue, May 19, 2015 at 02:05:04PM +0530, Archit Taneja wrote:
>>>> +void drm_bridge_post_dis
On 05/20/2015 12:05 PM, Daniel Vetter wrote:
> On Wed, May 20, 2015 at 10:49:38AM +0530, Archit Taneja wrote:
>> On 05/19/2015 09:00 PM, Daniel Vetter wrote:
>>> On Tue, May 19, 2015 at 04:37:44PM +0530, Archit Taneja wrote:
>>>> On 05/19/2015 03:04 PM, Daniel Vett
ans up the atomic and crtc helper files a bit.
Reviewed-by: Jani Nikula
Reviewed-by: Rob Clark
Reviewed-by: Daniel Vetter
Signed-off-by: Archit Taneja
---
v4:
- Fix up the call sequence for post_disable/pre_enable as suggested by
Daniel
v3:
- Add headerdocs for the new functions
v2:
- Add EXPORT_
Add DOC sections giving an overview of drm_bridge and how to fill up the
drm_bridge_funcs ops. Add these to drm.tpml in DocBook.
Add headerdocs for funcs in drm_bridge.c that don't have them yet.
Signed-off-by: Archit Taneja
---
Documentation/DocBook/drm.tmpl | 12 ++
drivers/gp
On 05/22/2015 07:46 PM, Hai Li wrote:
> DSI video mode engine can only take active-high sync signals. This
> change prevents MDP5 sending active-low sync signals to DSI in any
> case.
>
> Signed-off-by: Hai Li
Tested-by: Archit Taneja
> ---
> drivers/gpu/drm/msm/mdp/mdp
301 - 400 of 1388 matches
Mail list logo
