Re: [RFC] component: Fix: Unassign components' masters if bringing up master fails

On 02/16/2016 01:02 AM, Jon Medhurst (Tixy) wrote: On Thu, 2016-02-11 at 15:05 +0530, Archit Taneja wrote: component_master_add_with_match can fail if the master's bind op doesn't go through successfully. In such a scenario, all the components in the master's match array have their 'master

Re: [RFC] component: Fix: Unassign components' masters if bringing up master fails

On 02/16/2016 01:02 AM, Jon Medhurst (Tixy) wrote: On Thu, 2016-02-11 at 15:05 +0530, Archit Taneja wrote: component_master_add_with_match can fail if the master's bind op doesn't go through successfully. In such a scenario, all the components in the master's match array have their 'master

[PATCH v5 1/5] drm/dsi: check for CONFIG_OF when defining of_mipi_dsi_device_add

of_mipi_dsi_device_add is used only when CONFIG_OF is enabled. It currently works if OF support is disabled, but this will change when we add more functionality to it. Define the original func if CONFIG_OF is enabled. Define a dummy func otherwise. Signed-off-by: Archit Taneja --- drivers/gpu

[PATCH v5 4/5] drm/dsi: Add routine to unregister a DSI device

thing. Reviewed-by: Andrzej Hajda Signed-off-by: Archit Taneja --- drivers/gpu/drm/drm_mipi_dsi.c | 12 +++- include/drm/drm_mipi_dsi.h | 1 + 2 files changed, 12 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/drm_mipi_dsi.c b/drivers/gpu/drm/drm_mipi_dsi.c index 42a7aac

[PATCH v5 0/5] drm/dsi: DSI for devices with different control bus

d htmldocs warnings. Archit Taneja (5): drm/dsi: check for CONFIG_OF when defining of_mipi_dsi_device_add drm/dsi: Use mipi_dsi_device_register_full for DSI device creation drm/dsi: Try to match non-DT DSI devices drm/dsi: Add routine to unregister a DSI device drm/dsi: Get DSI host by DT d

[PATCH v5 3/5] drm/dsi: Try to match non-DT DSI devices

or the DSI bus. Reviewed-by: Andrzej Hajda Signed-off-by: Archit Taneja --- drivers/gpu/drm/drm_mipi_dsi.c | 18 +- include/drm/drm_mipi_dsi.h | 10 -- 2 files changed, 25 insertions(+), 3 deletions(-) diff --git a/drivers/gpu/drm/drm_mipi_dsi.c b/drivers/gpu/drm/drm_

[PATCH v5 5/5] drm/dsi: Get DSI host by DT device node

the hosts DSI that are currently registered. This list will be used to find the mipi_dsi_host corresponding to the device_node passed in of_find_mipi_dsi_host_by_node. Reviewed-by: Andrzej Hajda Signed-off-by: Archit Taneja --- drivers/gpu/drm/drm_mipi_dsi.c | 39

[PATCH v5 2/5] drm/dsi: Use mipi_dsi_device_register_full for DSI device creation

mipi_dsi_device_info and call this function. For DSI devices available via DT, of_mipi_dsi_device_add is used as before, but this now calls mipi_dsi_device_register_full internally. Signed-off-by: Archit Taneja --- drivers/gpu/drm/drm_mipi_dsi.c | 64 +++--- include/drm

[PATCH v5 2/5] drm/dsi: Use mipi_dsi_device_register_full for DSI device creation

mipi_dsi_device_info and call this function. For DSI devices available via DT, of_mipi_dsi_device_add is used as before, but this now calls mipi_dsi_device_register_full internally. Signed-off-by: Archit Taneja <arch...@codeaurora.org> --- drivers/gpu/drm/drm_mipi_dsi.

[PATCH v5 0/5] drm/dsi: DSI for devices with different control bus

d htmldocs warnings. Archit Taneja (5): drm/dsi: check for CONFIG_OF when defining of_mipi_dsi_device_add drm/dsi: Use mipi_dsi_device_register_full for DSI device creation drm/dsi: Try to match non-DT DSI devices drm/dsi: Add routine to unregister a DSI device drm/dsi: Get DSI host by DT d

[PATCH v5 3/5] drm/dsi: Try to match non-DT DSI devices

or the DSI bus. Reviewed-by: Andrzej Hajda <a.ha...@samsung.com> Signed-off-by: Archit Taneja <arch...@codeaurora.org> --- drivers/gpu/drm/drm_mipi_dsi.c | 18 +- include/drm/drm_mipi_dsi.h | 10 -- 2 files changed, 25 insertions(+), 3 deletions(-) diff -

[PATCH v5 5/5] drm/dsi: Get DSI host by DT device node

the hosts DSI that are currently registered. This list will be used to find the mipi_dsi_host corresponding to the device_node passed in of_find_mipi_dsi_host_by_node. Reviewed-by: Andrzej Hajda <a.ha...@samsung.com> Signed-off-by: Archit Taneja <arch...@codeaurora.org> --- dri

[PATCH v5 4/5] drm/dsi: Add routine to unregister a DSI device

thing. Reviewed-by: Andrzej Hajda <a.ha...@samsung.com> Signed-off-by: Archit Taneja <arch...@codeaurora.org> --- drivers/gpu/drm/drm_mipi_dsi.c | 12 +++- include/drm/drm_mipi_dsi.h | 1 + 2 files changed, 12 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/drm_

[PATCH v5 1/5] drm/dsi: check for CONFIG_OF when defining of_mipi_dsi_device_add

of_mipi_dsi_device_add is used only when CONFIG_OF is enabled. It currently works if OF support is disabled, but this will change when we add more functionality to it. Define the original func if CONFIG_OF is enabled. Define a dummy func otherwise. Signed-off-by: Archit Taneja <a

[RFC] component: Fix: Unassign components' masters if bringing up master fails

quot; Add 'master_remove_components' which sets the all the components's masters in the match array to NULL. This function is also re-used in component_master_del and replaces code that did the same thing. Signed-off-by: Archit Taneja --- drivers/base/compon

[RFC] component: Fix: Unassign components' masters if bringing up master fails

quot; Add 'master_remove_components' which sets the all the components's masters in the match array to NULL. This function is also re-used in component_master_del and replaces code that did the same thing. Signed-off-by: Archit Taneja <arch...@codeaurora.org> --- drivers/base/

Re: [PATCH v7 0/5] Add mipi dsi support for rk3288

On 02/08/2016 04:22 PM, Heiko Stuebner wrote: Hi Archit, Am Montag, 8. Februar 2016, 15:42:04 schrieb Archit Taneja: On 01/06/2016 09:33 AM, Chris Zhong wrote: The rk3288 MIPI DSI is a Synopsys DesignWare MIPI DSI host controller IP. This series adds support for a Synopsys DesignWare MIPI

Re: [PATCH v7 0/5] Add mipi dsi support for rk3288

Hi, On 01/06/2016 09:33 AM, Chris Zhong wrote: The rk3288 MIPI DSI is a Synopsys DesignWare MIPI DSI host controller IP. This series adds support for a Synopsys DesignWare MIPI DSI host controller DRM driver. The MIPI DSI feature is tested on rk3288 evb board, backport them to chrome os

Re: [PATCH v7 0/5] Add mipi dsi support for rk3288

Hi, On 01/06/2016 09:33 AM, Chris Zhong wrote: The rk3288 MIPI DSI is a Synopsys DesignWare MIPI DSI host controller IP. This series adds support for a Synopsys DesignWare MIPI DSI host controller DRM driver. The MIPI DSI feature is tested on rk3288 evb board, backport them to chrome os

Re: [PATCH v7 0/5] Add mipi dsi support for rk3288

On 02/08/2016 04:22 PM, Heiko Stuebner wrote: Hi Archit, Am Montag, 8. Februar 2016, 15:42:04 schrieb Archit Taneja: On 01/06/2016 09:33 AM, Chris Zhong wrote: The rk3288 MIPI DSI is a Synopsys DesignWare MIPI DSI host controller IP. This series adds support for a Synopsys DesignWare MIPI

Re: [PATCH] drm/msm/dsi: fix definition of msm_dsi_pll_28nm_8960_init()

/dsi_pll.o:dsi_pll.c:(.text+0x0): first defined here Thanks for the fix. Acked-by: Archit Taneja Dave, Could you please queue this for the next -rc cycle since it causes a build break? Thanks, Archit Signed-off-by: Luis Henriques --- drivers/gpu/drm/msm/dsi/pll/dsi_pll.h | 4 ++-- 1 file

Re: [PATCH] drm/msm/dsi: fix definition of msm_dsi_pll_28nm_8960_init()

/dsi_pll.o:dsi_pll.c:(.text+0x0): first defined here Thanks for the fix. Acked-by: Archit Taneja <arch...@codeaurora.org> Dave, Could you please queue this for the next -rc cycle since it causes a build break? Thanks, Archit Signed-off-by: Luis Henriques <luis.henriq...@canonical.com> -

Re: [PATCH wq/for-4.5-fixes] workqueue: skip flush dependency checks for legacy workqueues

On 01/29/2016 04:29 PM, Tejun Heo wrote: fca839c00a12 ("workqueue: warn if memory reclaim tries to flush !WQ_MEM_RECLAIM workqueue") implemented flush dependency warning which triggers if a PF_MEMALLOC task or WQ_MEM_RECLAIM workqueue tries to flush a !WQ_MEM_RECLAIM workquee. This assumes

Re: BUG caused by "Use new drm_fb_helper functions" series

Hi Peter, On 02/02/2016 02:07 AM, Peter Hurley wrote: Hi Archit, Just booting 4.4-rc5+, I got this splat [1] At first glance, this appears to be a simple fix. Thanks for sharing this. However, I'm concerned that fbcon functions, which may be called with interrupts disabled, are now hooked

Re: [PATCH wq/for-4.5-fixes] workqueue: skip flush dependency checks for legacy workqueues

On 01/29/2016 04:29 PM, Tejun Heo wrote: fca839c00a12 ("workqueue: warn if memory reclaim tries to flush !WQ_MEM_RECLAIM workqueue") implemented flush dependency warning which triggers if a PF_MEMALLOC task or WQ_MEM_RECLAIM workqueue tries to flush a !WQ_MEM_RECLAIM workquee. This assumes

Re: BUG caused by "Use new drm_fb_helper functions" series

Hi Peter, On 02/02/2016 02:07 AM, Peter Hurley wrote: Hi Archit, Just booting 4.4-rc5+, I got this splat [1] At first glance, this appears to be a simple fix. Thanks for sharing this. However, I'm concerned that fbcon functions, which may be called with interrupts disabled, are now hooked

Re: [PATCH v4 6/6] drm/dsi: Get DSI host by DT device node

On 01/21/2016 09:46 PM, Thierry Reding wrote: On Thu, Dec 10, 2015 at 06:11:40PM +0530, Archit Taneja wrote: mipi_dsi_devices are inherently aware of their host because they share a parent-child hierarchy in the device tree. non-dsi drivers that create dsi device don't have this data

Re: [PATCH v4 5/6] drm/dsi: Add routine to unregister dsi device

On 01/21/2016 09:42 PM, Thierry Reding wrote: On Thu, Dec 10, 2015 at 06:11:39PM +0530, Archit Taneja wrote: A driver calling mipi_dsi_device_new might want to unregister the device once it's done. It might also require it in an error handling path in case something didn't go right. Reviewed

Re: [PATCH v4 4/6] drm/dsi: Check for used channels

On 01/21/2016 09:41 PM, Thierry Reding wrote: On Thu, Dec 10, 2015 at 06:11:38PM +0530, Archit Taneja wrote: We don't check whether a previously registered mipi_dsi_device under the same host shares the same virtual channel. Before registering, check if any of the registered devices doesn't

Re: [PATCH v4 3/6] drm/dsi: Try to match non-DT dsi devices

On 1/21/2016 9:35 PM, Thierry Reding wrote: On Thu, Dec 10, 2015 at 06:11:37PM +0530, Archit Taneja wrote: Add a device name field in mipi_dsi_device. This name is different from the actual dev name (which is of the format "hostname.reg"). When the device is created via DT, this n

Re: [PATCH v4 2/6] drm/dsi: Refactor device creation

On 1/21/2016 9:16 PM, Thierry Reding wrote: On Thu, Dec 10, 2015 at 06:11:36PM +0530, Archit Taneja wrote: Simplify the mipi dsi device creation process. device_initialize and "MIPI" and "DSI", please. Sure, I'll replace with these and in the other patches. d

Re: [PATCH v4 1/6] drm/dsi: check for CONFIG_OF when defining of_mipi_dsi_device_add

On 1/21/2016 9:01 PM, Thierry Reding wrote: On Thu, Dec 10, 2015 at 06:11:35PM +0530, Archit Taneja wrote: of_mipi_dsi_device_add is used only when CONFIG_OF is enabled. It currently works if OF support is disabled, but this will change when we add more functionality to it. Define

Re: [PATCH v4 5/6] drm/dsi: Add routine to unregister dsi device

On 01/21/2016 09:42 PM, Thierry Reding wrote: On Thu, Dec 10, 2015 at 06:11:39PM +0530, Archit Taneja wrote: A driver calling mipi_dsi_device_new might want to unregister the device once it's done. It might also require it in an error handling path in case something didn't go right. Reviewed

Re: [PATCH v4 4/6] drm/dsi: Check for used channels

On 01/21/2016 09:41 PM, Thierry Reding wrote: On Thu, Dec 10, 2015 at 06:11:38PM +0530, Archit Taneja wrote: We don't check whether a previously registered mipi_dsi_device under the same host shares the same virtual channel. Before registering, check if any of the registered devices doesn't

Re: [PATCH v4 6/6] drm/dsi: Get DSI host by DT device node

On 01/21/2016 09:46 PM, Thierry Reding wrote: On Thu, Dec 10, 2015 at 06:11:40PM +0530, Archit Taneja wrote: mipi_dsi_devices are inherently aware of their host because they share a parent-child hierarchy in the device tree. non-dsi drivers that create dsi device don't have this data

Re: [PATCH v4 1/6] drm/dsi: check for CONFIG_OF when defining of_mipi_dsi_device_add

On 1/21/2016 9:01 PM, Thierry Reding wrote: On Thu, Dec 10, 2015 at 06:11:35PM +0530, Archit Taneja wrote: of_mipi_dsi_device_add is used only when CONFIG_OF is enabled. It currently works if OF support is disabled, but this will change when we add more functionality to it. Define

Re: [PATCH v4 2/6] drm/dsi: Refactor device creation

On 1/21/2016 9:16 PM, Thierry Reding wrote: On Thu, Dec 10, 2015 at 06:11:36PM +0530, Archit Taneja wrote: Simplify the mipi dsi device creation process. device_initialize and "MIPI" and "DSI", please. Sure, I'll replace with these and in the other patches. d

Re: [PATCH v4 3/6] drm/dsi: Try to match non-DT dsi devices

On 1/21/2016 9:35 PM, Thierry Reding wrote: On Thu, Dec 10, 2015 at 06:11:37PM +0530, Archit Taneja wrote: Add a device name field in mipi_dsi_device. This name is different from the actual dev name (which is of the format "hostname.reg"). When the device is created via DT, this n

Re: [PATCH v2 1/2] drm: bridge: sil902x

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 log, there's no

Re: [PATCH v2 1/2] drm: bridge: sil902x

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

Re: [PATCH v4 0/6] drm/dsi: DSI for devices with different control bus

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 example, DSI

Re: [PATCH v4 0/6] drm/dsi: DSI for devices with different control bus

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 example, DSI

Re: [PATCH v4 2/5] mtd: nand: Qualcomm NAND controller driver

On 12/16/2015 07:48 PM, Boris Brezillon wrote: On Wed, 16 Dec 2015 17:27:48 +0530 Archit Taneja wrote: +/* + * NAND controller page layout info + * + * |---| |-| + * | xx...xx| | *xx...xx

Re: [PATCH v4 2/5] mtd: nand: Qualcomm NAND controller driver

On 12/16/2015 07:48 PM, Boris Brezillon wrote: On Wed, 16 Dec 2015 17:27:48 +0530 Archit Taneja <arch...@codeaurora.org> wrote: +/* + * NAND controller page layout info + * + * |---| |-| + * | xx...

Re: [PATCH v4 2/5] mtd: nand: Qualcomm NAND controller driver

Hi Boris, On 12/16/2015 02:45 PM, Boris Brezillon wrote: Hi Archit, Again, sorry for the late review. It's probably not exhaustive but points a few things that should be fixed. Thanks for the thorough review! Some comments below. On Wed, 19 Aug 2015 10:19:03 +0530 Archit Taneja wrote

Re: [PATCH v4 3/5] dt/bindings: qcom_nandc: Add DT bindings

Hi Boris, On 12/16/2015 12:03 PM, Boris Brezillon wrote: Hi Archit, Sorry for the late review, but there are a few things I think should be addressed. On Wed, 19 Aug 2015 10:19:04 +0530 Archit Taneja wrote: Add DT bindings document for the Qualcomm NAND controller driver. Cc: devicet

Re: [PATCH v4 2/5] mtd: nand: Qualcomm NAND controller driver

Hi Boris, On 12/16/2015 02:45 PM, Boris Brezillon wrote: Hi Archit, Again, sorry for the late review. It's probably not exhaustive but points a few things that should be fixed. Thanks for the thorough review! Some comments below. On Wed, 19 Aug 2015 10:19:03 +0530 Archit Taneja <a

Re: [PATCH v4 3/5] dt/bindings: qcom_nandc: Add DT bindings

Hi Boris, On 12/16/2015 12:03 PM, Boris Brezillon wrote: Hi Archit, Sorry for the late review, but there are a few things I think should be addressed. On Wed, 19 Aug 2015 10:19:04 +0530 Archit Taneja <arch...@codeaurora.org> wrote: Add DT bindings document for the Qualcomm NAND cont

Re: [PATCH v6 2/2] drm/bridge: Add I2C based driver for ps8640 bridge

Hi, On 12/15/2015 09:00 AM, Jitao Shi wrote: This patch adds drm_bridge driver for parade DSI to eDP bridge chip. Signed-off-by: Jitao Shi --- Changes since v5 -fix compile errors when CONFIG_GPIOLIB=n --- drivers/gpu/drm/bridge/Kconfig | 10 + drivers/gpu/drm/bridge/Makefile

Re: [PATCH v6 2/2] drm/bridge: Add I2C based driver for ps8640 bridge

Hi, On 12/15/2015 09:00 AM, Jitao Shi wrote: This patch adds drm_bridge driver for parade DSI to eDP bridge chip. Signed-off-by: Jitao Shi --- Changes since v5 -fix compile errors when CONFIG_GPIOLIB=n --- drivers/gpu/drm/bridge/Kconfig | 10 +

[PATCH v4 0/6] drm/dsi: DSI for devices with different control bus

without the need of them to have a DT node. [1]: https://lkml.org/lkml/2015/6/30/42 Changes in v4: - Added a new patch that fixes build issues when CONFIG_OF is not set. Changes in v3: - Incorporated misc comments by Andrzej. Changed from RFC to a PATCH set. - Fixed htmldocs warnings. Archit

[PATCH v4 6/6] drm/dsi: Get DSI host by DT device node

the hosts DSI that are currently registered. This list will be used to find the mipi_dsi_host corresponding to the device_node passed in of_find_mipi_dsi_host_by_node. Reviewed-by: Andrzej Hajda Signed-off-by: Archit Taneja --- drivers/gpu/drm/drm_mipi_dsi.c | 38

[PATCH v4 5/6] drm/dsi: Add routine to unregister dsi device

A driver calling mipi_dsi_device_new might want to unregister the device once it's done. It might also require it in an error handling path in case something didn't go right. Reviewed-by: Andrzej Hajda Signed-off-by: Archit Taneja --- include/drm/drm_mipi_dsi.h | 5 + 1 file changed, 5

[PATCH v4 4/6] drm/dsi: Check for used channels

DT. Now that we also support creating devices manually, we could end up in a situation where a driver tries to create a device with a virtual channel already taken by a device populated in DT. Reviewed-by: Andrzej Hajda Signed-off-by: Archit Taneja --- drivers/gpu/drm/drm_mipi_dsi.c | 26

[PATCH v4 3/6] drm/dsi: Try to match non-DT dsi devices

or the dsi bus. Reviewed-by: Andrzej Hajda Signed-off-by: Archit Taneja --- drivers/gpu/drm/drm_mipi_dsi.c | 25 - include/drm/drm_mipi_dsi.h | 6 ++ 2 files changed, 30 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/drm_mipi_dsi.c b/drivers/gpu/drm/drm_

[PATCH v4 2/6] drm/dsi: Refactor device creation

as a standalone way to create a dsi device not available via DT. The new device creation process tries to closely follow what's been done in i2c_new_device in i2c-core. Reviewed-by: Andrzej Hajda Signed-off-by: Archit Taneja --- drivers/gpu/drm/drm_mipi_dsi.c | 61

[PATCH v4 1/6] drm/dsi: check for CONFIG_OF when defining of_mipi_dsi_device_add

of_mipi_dsi_device_add is used only when CONFIG_OF is enabled. It currently works if OF support is disabled, but this will change when we add more functionality to it. Define the original func if CONFIG_OF is enabled. Define a dummy func otherwise. Signed-off-by: Archit Taneja --- drivers/gpu

[PATCH v4 0/6] drm/dsi: DSI for devices with different control bus

without the need of them to have a DT node. [1]: https://lkml.org/lkml/2015/6/30/42 Changes in v4: - Added a new patch that fixes build issues when CONFIG_OF is not set. Changes in v3: - Incorporated misc comments by Andrzej. Changed from RFC to a PATCH set. - Fixed htmldocs warnings. Archit

[PATCH v4 6/6] drm/dsi: Get DSI host by DT device node

the hosts DSI that are currently registered. This list will be used to find the mipi_dsi_host corresponding to the device_node passed in of_find_mipi_dsi_host_by_node. Reviewed-by: Andrzej Hajda <a.ha...@samsung.com> Signed-off-by: Archit Taneja <arch...@codeaurora.org> --- dri

[PATCH v4 4/6] drm/dsi: Check for used channels

DT. Now that we also support creating devices manually, we could end up in a situation where a driver tries to create a device with a virtual channel already taken by a device populated in DT. Reviewed-by: Andrzej Hajda <a.ha...@samsung.com> Signed-off-by: Archit Taneja <arch...@codea

[PATCH v4 5/6] drm/dsi: Add routine to unregister dsi device

A driver calling mipi_dsi_device_new might want to unregister the device once it's done. It might also require it in an error handling path in case something didn't go right. Reviewed-by: Andrzej Hajda <a.ha...@samsung.com> Signed-off-by: Archit Taneja <arch...@codeaurora.org> ---

[PATCH v4 3/6] drm/dsi: Try to match non-DT dsi devices

or the dsi bus. Reviewed-by: Andrzej Hajda <a.ha...@samsung.com> Signed-off-by: Archit Taneja <arch...@codeaurora.org> --- drivers/gpu/drm/drm_mipi_dsi.c | 25 - include/drm/drm_mipi_dsi.h | 6 ++ 2 files changed, 30 insertions(+), 1 deletion(-) diff -

[PATCH v4 2/6] drm/dsi: Refactor device creation

as a standalone way to create a dsi device not available via DT. The new device creation process tries to closely follow what's been done in i2c_new_device in i2c-core. Reviewed-by: Andrzej Hajda <a.ha...@samsung.com> Signed-off-by: Archit Taneja <arch...@codeaurora.org> --- drivers/gpu/drm/dr

[PATCH v4 1/6] drm/dsi: check for CONFIG_OF when defining of_mipi_dsi_device_add

of_mipi_dsi_device_add is used only when CONFIG_OF is enabled. It currently works if OF support is disabled, but this will change when we add more functionality to it. Define the original func if CONFIG_OF is enabled. Define a dummy func otherwise. Signed-off-by: Archit Taneja <a

Re: [PATCH v3 2/5] drm/dsi: Try to match non-DT dsi devices

On 12/07/2015 02:40 PM, Jani Nikula wrote: On Mon, 07 Dec 2015, Archit Taneja wrote: On 12/07/2015 02:15 PM, Jani Nikula wrote: On Mon, 07 Dec 2015, Archit Taneja wrote: Hi, On 11/30/2015 06:15 PM, kbuild test robot wrote: Hi Archit, [auto build test ERROR on: v4.4-rc3] [also build

Re: [PATCH v3 2/5] drm/dsi: Try to match non-DT dsi devices

On 12/07/2015 02:15 PM, Jani Nikula wrote: On Mon, 07 Dec 2015, Archit Taneja wrote: Hi, On 11/30/2015 06:15 PM, kbuild test robot wrote: Hi Archit, [auto build test ERROR on: v4.4-rc3] [also build test ERROR on: next-20151127] url: https://github.com/0day-ci/linux/commits/Archit

Re: [PATCH v3 2/5] drm/dsi: Try to match non-DT dsi devices

On 12/07/2015 02:40 PM, Jani Nikula wrote: On Mon, 07 Dec 2015, Archit Taneja <arch...@codeaurora.org> wrote: On 12/07/2015 02:15 PM, Jani Nikula wrote: On Mon, 07 Dec 2015, Archit Taneja <arch...@codeaurora.org> wrote: Hi, On 11/30/2015 06:15 PM, kbuild test robot wrote

Re: [PATCH v3 2/5] drm/dsi: Try to match non-DT dsi devices

On 12/07/2015 02:15 PM, Jani Nikula wrote: On Mon, 07 Dec 2015, Archit Taneja <arch...@codeaurora.org> wrote: Hi, On 11/30/2015 06:15 PM, kbuild test robot wrote: Hi Archit, [auto build test ERROR on: v4.4-rc3] [also build test ERROR on: next-20151127] url: https://github.com/0

Re: [PATCH v3 2/5] drm/dsi: Try to match non-DT dsi devices

Hi, On 11/30/2015 06:15 PM, kbuild test robot wrote: Hi Archit, [auto build test ERROR on: v4.4-rc3] [also build test ERROR on: next-20151127] url: https://github.com/0day-ci/linux/commits/Archit-Taneja/drm-dsi-DSI-for-devices-with-different-control-bus/20151130-200725 config: x86_64

Re: [PATCH v3 2/5] drm/dsi: Try to match non-DT dsi devices

Hi, On 11/30/2015 06:15 PM, kbuild test robot wrote: Hi Archit, [auto build test ERROR on: v4.4-rc3] [also build test ERROR on: next-20151127] url: https://github.com/0day-ci/linux/commits/Archit-Taneja/drm-dsi-DSI-for-devices-with-different-control-bus/20151130-200725 config: x86_64

[PATCH v3 1/5] drm/dsi: Refactor device creation

as a standalone way to create a dsi device not available via DT. The new device creation process tries to closely follow what's been done in i2c_new_device in i2c-core. Reviewed-by: Andrzej Hajda Signed-off-by: Archit Taneja --- drivers/gpu/drm/drm_mipi_dsi.c | 61

[PATCH v3 5/5] drm/dsi: Get DSI host by DT device node

the hosts DSI that are currently registered. This list will be used to find the mipi_dsi_host corresponding to the device_node passed in of_find_mipi_dsi_host_by_node. Reviewed-by: Andrzej Hajda Signed-off-by: Archit Taneja --- drivers/gpu/drm/drm_mipi_dsi.c | 38

[PATCH v3 0/5] drm/dsi: DSI for devices with different control bus

without the need of them to have a DT node. [1]: https://lkml.org/lkml/2015/6/30/42 Changes from v2 to v3: - Incorporated misc comments by Andrzej. Changed from RFC to a PATCH set. - Fixed htmldocs warnings. Archit Taneja (5): drm/dsi: Refactor device creation drm/dsi: Try to match non-DT dsi

[PATCH v3 4/5] drm/dsi: Add routine to unregister dsi device

A driver calling mipi_dsi_device_new might want to unregister the device once it's done. It might also require it in an error handling path in case something didn't go right. Signed-off-by: Archit Taneja --- include/drm/drm_mipi_dsi.h | 5 + 1 file changed, 5 insertions(+) diff --git

[PATCH v3 3/5] drm/dsi: Check for used channels

DT. Now that we also support creating devices manually, we could end up in a situation where a driver tries to create a device with a virtual channel already taken by a device populated in DT. Reviewed-by: Andrzej Hajda Signed-off-by: Archit Taneja --- drivers/gpu/drm/drm_mipi_dsi.c | 26

[PATCH v3 2/5] drm/dsi: Try to match non-DT dsi devices

or the dsi bus. Reviewed-by: Andrzej Hajda Signed-off-by: Archit Taneja --- drivers/gpu/drm/drm_mipi_dsi.c | 25 - include/drm/drm_mipi_dsi.h | 6 ++ 2 files changed, 30 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/drm_mipi_dsi.c b/drivers/gpu/drm/drm_

[PATCH v3 0/5] drm/dsi: DSI for devices with different control bus

without the need of them to have a DT node. [1]: https://lkml.org/lkml/2015/6/30/42 Changes from v2 to v3: - Incorporated misc comments by Andrzej. Changed from RFC to a PATCH set. - Fixed htmldocs warnings. Archit Taneja (5): drm/dsi: Refactor device creation drm/dsi: Try to match non-DT dsi

[PATCH v3 2/5] drm/dsi: Try to match non-DT dsi devices

or the dsi bus. Reviewed-by: Andrzej Hajda <a.ha...@samsung.com> Signed-off-by: Archit Taneja <arch...@codeaurora.org> --- drivers/gpu/drm/drm_mipi_dsi.c | 25 - include/drm/drm_mipi_dsi.h | 6 ++ 2 files changed, 30 insertions(+), 1 deletion(-) diff -

[PATCH v3 5/5] drm/dsi: Get DSI host by DT device node

the hosts DSI that are currently registered. This list will be used to find the mipi_dsi_host corresponding to the device_node passed in of_find_mipi_dsi_host_by_node. Reviewed-by: Andrzej Hajda <a.ha...@samsung.com> Signed-off-by: Archit Taneja <arch...@codeaurora.org> --- dri

[PATCH v3 4/5] drm/dsi: Add routine to unregister dsi device

A driver calling mipi_dsi_device_new might want to unregister the device once it's done. It might also require it in an error handling path in case something didn't go right. Signed-off-by: Archit Taneja <arch...@codeaurora.org> --- include/drm/drm_mipi_dsi.h | 5 + 1 file chan

[PATCH v3 3/5] drm/dsi: Check for used channels

DT. Now that we also support creating devices manually, we could end up in a situation where a driver tries to create a device with a virtual channel already taken by a device populated in DT. Reviewed-by: Andrzej Hajda <a.ha...@samsung.com> Signed-off-by: Archit Taneja <arch...@codea

[PATCH v3 1/5] drm/dsi: Refactor device creation

as a standalone way to create a dsi device not available via DT. The new device creation process tries to closely follow what's been done in i2c_new_device in i2c-core. Reviewed-by: Andrzej Hajda <a.ha...@samsung.com> Signed-off-by: Archit Taneja <arch...@codeaurora.org> --- drivers/gpu/drm/dr

Re: [PATCH v4 1/5] mtd: nand: Create a BBT flag to access bad block markers in raw mode

Hi, On 10/12/2015 01:33 AM, Brian Norris wrote: Hi Boris, On Fri, Oct 02, 2015 at 08:27:38AM +0200, Boris Brezillon wrote: Brian, Archit, On Thu, 1 Oct 2015 19:44:34 -0700 Brian Norris wrote: On Wed, Aug 19, 2015 at 10:19:02AM +0530, Archit Taneja wrote: Some controllers can access

Re: [PATCH v4 1/5] mtd: nand: Create a BBT flag to access bad block markers in raw mode

Hi, On 10/12/2015 01:33 AM, Brian Norris wrote: Hi Boris, On Fri, Oct 02, 2015 at 08:27:38AM +0200, Boris Brezillon wrote: Brian, Archit, On Thu, 1 Oct 2015 19:44:34 -0700 Brian Norris <computersforpe...@gmail.com> wrote: On Wed, Aug 19, 2015 at 10:19:02AM +0530, Archit Taneja wrote:

Re: [PATCH v2 2/2] drm/panel: Add Sharp LS043T1LE01 MIPI DSI panel

On 10/31/2015 04:04 AM, Bjorn Andersson wrote: From: Werner Johansson This adds support for the Sharp panel found on the Qualcomm Snapdragon 800 Dragonboard (APQ8074) Signed-off-by: Werner Johansson Signed-off-by: Bjorn Andersson Reviewed-by: Archit Taneja --- Change since v1

Re: [PATCH v2 2/2] drm/panel: Add Sharp LS043T1LE01 MIPI DSI panel

ff-by: Bjorn Andersson <bjorn.anders...@sonymobile.com> Reviewed-by: Archit Taneja <arch...@codeaurora.org> --- Change since v1: - Dropped -vid suffix from compatible drivers/gpu/drm/panel/Kconfig | 9 + drivers/gpu/drm/panel/Makefile | 1 +

Re: [RFC v2 4/5] drm/dsi: Add routine to unregister dsi device

On 11/02/2015 04:12 PM, Andrzej Hajda wrote: On 11/02/2015 07:28 AM, Archit Taneja wrote: On 10/30/2015 07:51 PM, Andrzej Hajda wrote: On 10/06/2015 11:24 AM, Archit Taneja wrote: A driver calling mipi_dsi_device_new might want to unregister the device once it's done. It might also require

Re: [RFC v2 5/5] drm/dsi: Get DSI host by DT device node

On 11/02/2015 04:20 PM, Andrzej Hajda wrote: On 10/06/2015 11:24 AM, Archit Taneja wrote: mipi_dsi_devices are inherently aware of their host because they share a parent-child hierarchy in the device tree. Non-dsi drivers that create a dummy dsi device don't have this data. In order to get

Re: [RFC v2 4/5] drm/dsi: Add routine to unregister dsi device

On 11/02/2015 04:12 PM, Andrzej Hajda wrote: On 11/02/2015 07:28 AM, Archit Taneja wrote: On 10/30/2015 07:51 PM, Andrzej Hajda wrote: On 10/06/2015 11:24 AM, Archit Taneja wrote: A driver calling mipi_dsi_device_new might want to unregister the device once it's done. It might also require

Re: [RFC v2 5/5] drm/dsi: Get DSI host by DT device node

On 11/02/2015 04:20 PM, Andrzej Hajda wrote: On 10/06/2015 11:24 AM, Archit Taneja wrote: mipi_dsi_devices are inherently aware of their host because they share a parent-child hierarchy in the device tree. Non-dsi drivers that create a dummy dsi device don't have this data. In order to get

Re: [RFC v2 4/5] drm/dsi: Add routine to unregister dsi device

On 10/30/2015 07:51 PM, Andrzej Hajda wrote: On 10/06/2015 11:24 AM, Archit Taneja wrote: A driver calling mipi_dsi_device_new might want to unregister the device once it's done. It might also require it in an error handling path in case something didn't go right. When the dsi host driver

Re: [RFC v2 3/5] drm/dsi: Check for used channels

On 10/30/2015 06:22 PM, Andrzej Hajda wrote: On 10/06/2015 11:24 AM, Archit Taneja wrote: We don't check whether a previously registered mipi_dsi_device under the same host shares the same virtual channel. Before registering, check if any of the registered devices doesn't already have

Re: [RFC v2 2/5] drm/dsi: Try to match non-DT dsi devices

On 10/30/2015 06:12 PM, Andrzej Hajda wrote: On 10/06/2015 11:24 AM, Archit Taneja wrote: Add a device name field in mipi_dsi_device. This name is different from the actual dev name (which is of the format "hostname.reg"). When the device is created via DT, this name is set to th

Re: [RFC v2 2/5] drm/dsi: Try to match non-DT dsi devices

On 10/30/2015 06:12 PM, Andrzej Hajda wrote: On 10/06/2015 11:24 AM, Archit Taneja wrote: Add a device name field in mipi_dsi_device. This name is different from the actual dev name (which is of the format "hostname.reg"). When the device is created via DT, this name is set to th

Re: [RFC v2 4/5] drm/dsi: Add routine to unregister dsi device

On 10/30/2015 07:51 PM, Andrzej Hajda wrote: On 10/06/2015 11:24 AM, Archit Taneja wrote: A driver calling mipi_dsi_device_new might want to unregister the device once it's done. It might also require it in an error handling path in case something didn't go right. When the dsi host driver

Re: [RFC v2 3/5] drm/dsi: Check for used channels

On 10/30/2015 06:22 PM, Andrzej Hajda wrote: On 10/06/2015 11:24 AM, Archit Taneja wrote: We don't check whether a previously registered mipi_dsi_device under the same host shares the same virtual channel. Before registering, check if any of the registered devices doesn't already have

Re: [PATCH] clk: qcom: msm8960: Fix dsi1/2 halt bits

go away. Fixes: 5532cfb567fe ("clk: qcom: mmcc-8960: Add DSI related clocks") Cc: Archit Taneja Signed-off-by: Stephen Boyd --- Acked-by: Archit Taneja -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation -- To unsubs

Re: [PATCH] clk: qcom: msm8960: Fix dsi1/2 halt bits

go away. Fixes: 5532cfb567fe ("clk: qcom: mmcc-8960: Add DSI related clocks") Cc: Archit Taneja <arch...@codeaurora.org> Signed-off-by: Stephen Boyd <sb...@codeaurora.org> --- Acked-by: Archit Taneja <arch...@codeaurora.org> -- The Qualcomm Innovation Center, Inc. is

Re: [PATCH v4 2/5] mtd: nand: Qualcomm NAND controller driver

Hi, On 10/06/2015 02:47 PM, Brian Norris wrote: Hi Archit, On Mon, Oct 05, 2015 at 12:21:54PM +0530, Archit Taneja wrote: On 10/02/2015 08:35 AM, Brian Norris wrote: On Wed, Aug 19, 2015 at 10:19:03AM +0530, Archit Taneja wrote: The Qualcomm NAND controller is found in SoCs like IPQ806x

[RFC v2 3/5] drm/dsi: Check for used channels

DT. Now that we also support creating devices manually, we could end up in a situation where a driver tries to create a device with a virtual channel already taken by a device populated in DT. Signed-off-by: Archit Taneja --- drivers/gpu/drm/drm_mipi_dsi.c | 26 -- 1 file

<    1   2   3   4   5   6   7   8   9   >