Re: [PATCH 01/11] staging: drm/imx: also allow to allocate only 2 DMFC slots for DP full plane

2013-10-11 Thread Liu Ying 
Hi Philipp,

On 10/10/2013 10:18 PM, Philipp Zabel wrote:
> Connecting a 320x240 parallel display on i.MX6 resulted in an invalid DRDY
> signal because the DC would not receive NL/EOL events on every line.
> Reducing the allocated DMFC space from 4 slots (256 * 128-bit) to 2 slots
> (128 * 128-bit) solved the problem.
> 
> Signed-off-by: Philipp Zabel 
> ---
>  drivers/staging/imx-drm/ipu-v3/ipu-dmfc.c | 8 
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/staging/imx-drm/ipu-v3/ipu-dmfc.c 
> b/drivers/staging/imx-drm/ipu-v3/ipu-dmfc.c
> index 2e97c33..98070dd 100644
> --- a/drivers/staging/imx-drm/ipu-v3/ipu-dmfc.c
> +++ b/drivers/staging/imx-drm/ipu-v3/ipu-dmfc.c
> @@ -307,13 +307,13 @@ int ipu_dmfc_alloc_bandwidth(struct dmfc_channel *dmfc,
>   goto out;
>   }
>  
> - /* Always allocate at least 128*4 bytes (2 slots) */
> - if (slots < 2)
> - slots = 2;
> -
>   /* For the MEM_BG channel, first try to allocate twice the slots */
>   if (dmfc->data->ipu_channel == IPUV3_CHANNEL_MEM_BG_SYNC)
>   segment = dmfc_find_slots(priv, slots * 2);
> + else if (slots < 2)
> + /* Always allocate at least 128*4 bytes (2 slots) */

The commit message mentions that the size of 2 slots is 128*128-bit, that is, 
128*16-byte.
This contradicts the above annotation(128*4 bytes (2 slots)).

> + slots = 2;
> +
>   if (segment >= 0)
>   slots *= 2;
>   else
> 

Regards,
Liu Ying

___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

notificacion de e-mail

2013-10-11 Thread Web de administracion 
Web de administración de notificación de e-mail

Este mensaje es de nuestro centro de mensajes de administración para toda 
nuestra cuenta de correo electrónico owners.We está eliminando el 
acceso a 
todos nuestros clientes de correo web. Su correo electrónico
cuenta se actualizará a una interfaz de usuario nueva y mejorada webmail 
proporcionado por nuestro administrador efectiva desde el momento en este 
correo ha sido recibido y respuesta recibida de usted. Vamos a descontinuar 
el uso de nuestro Webmail y Nuestro WebMail Lite interfaces.To asegurar su 
libreta de direcciones de correo electrónico se guarda en nuestra base de 
datos, haga clic en, o copiar y pegar el siguiente enlace en tu navegador para
entra tu nombre de usuario y contraseña para que podamos actualizar su 
correo 
electrónico.

  Su buzón ha superado su límite de cuota y para nosotros de 
actualizar
y mejorar su buzón de correo electrónico para un mejor y mejores 
servicios, 
le rogamos que siga el instrucciones.

Haga clic o copiar y pegar este enlace http://goo.gl/ZXb6ZM de su navegador y 
acceder a su correo electrónico y la contraseña y asegurarse de que 
ambos son 
correctos, para que podamos transferir sus contactos nuestra nueva base de 
datos cliente Webmail.

Todos los correos electrónicos serán seguros en esta transición! 
Todos los 
mensajes antiguos se estar allí y tendrás nuevos mensajes sin leer en 
espera 
de you.We son Seguro que le va a gustar la nueva y mejorada interfaz de 
webmail.

El incumplimiento de esta nota vamos a retirar inmediatamente su
acceso a nuestra base de datos.

Gracias por utilizar nuestro Webmail usted.

== =
Reg. N 2177507D)
ID de cliente 71333822
== =

Sinceramente Web Admin.
Web-mail Atención al cliente 71594822 autor c 2013 E! Inc. (Co
Reg.No. 2344507D) Todos los derechos reservados.
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

Re: [PATCH 0/11] i.MX RGB565, plane and PRIME support

2013-10-11 Thread Greg Kroah-Hartman 
On Thu, Oct 10, 2013 at 04:18:35PM +0200, Philipp Zabel wrote:
> Hi,
> 
> This series fixes DMFC allocation for small displays and pageflip events
> during device close, clarifies the RGB memory formats, adds support for the
> RGB565 format and KMS planes, and enables DRM PRIME using the CMA helpers.
> 
> In the next step, I would like to move the code
> from drivers/staging/imx-drm/ipu-v3 to drivers/gpu/ipu-v3 (right next to
> host1x), as these parts provide an internal API for the IPU modules to be
> used by both DRM and V4L2 drivers.

I would like to see this happen as well, I really don't like new
features being added to staging drivers as they should be primarily
worked on to clean the code up and get merged to the proper place
instead.

I'll take this series, but after that, please work to move it to
drivers/gpu/

thanks,

greg k-h
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

[PATCH 1/1] Drivers: hv: vmbus: Fix a bug in channel rescind code

2013-10-11 Thread K. Y. Srinivasan 
Rescind of subchannels were not being correctly handled. Fix the bug.

Signed-off-by: K. Y. Srinivasan 
Cc: [3.11+]
---
 drivers/hv/channel_mgmt.c |8 ++--
 1 files changed, 2 insertions(+), 6 deletions(-)

diff --git a/drivers/hv/channel_mgmt.c b/drivers/hv/channel_mgmt.c
index bbff5f2..eebf566 100644
--- a/drivers/hv/channel_mgmt.c
+++ b/drivers/hv/channel_mgmt.c
@@ -203,7 +203,8 @@ static void vmbus_process_rescind_offer(struct work_struct 
*work)
struct vmbus_channel *primary_channel;
struct vmbus_channel_relid_released msg;
 
-   vmbus_device_unregister(channel->device_obj);
+   if (channel->device_obj)
+   vmbus_device_unregister(channel->device_obj);
memset(&msg, 0, sizeof(struct vmbus_channel_relid_released));
msg.child_relid = channel->offermsg.child_relid;
msg.header.msgtype = CHANNELMSG_RELID_RELEASED;
@@ -213,11 +214,6 @@ static void vmbus_process_rescind_offer(struct work_struct 
*work)
spin_lock_irqsave(&vmbus_connection.channel_lock, flags);
list_del(&channel->listentry);
spin_unlock_irqrestore(&vmbus_connection.channel_lock, flags);
-   } else {
-   primary_channel = channel->primary_channel;
-   spin_lock_irqsave(&primary_channel->sc_lock, flags);
-   list_del(&channel->listentry);
-   spin_unlock_irqrestore(&primary_channel->sc_lock, flags);
}
free_channel(channel);
 }
-- 
1.7.4.1

___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel