lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180430110418.5ba6baab@bbrezillon>
Date:   Mon, 30 Apr 2018 11:04:18 +0200
From:   Boris Brezillon <boris.brezillon@...tlin.com>
To:     Eric Anholt <eric@...olt.net>
Cc:     dri-devel@...ts.freedesktop.org,
        Thierry Reding <thierry.reding@...il.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] drm/panel: Enable DSI transactions on the RPi
 panel.

On Tue, 31 Oct 2017 12:32:58 -0700
Eric Anholt <eric@...olt.net> wrote:

> It turns out that I had just mistaken what type of write the register
> writes were supposed to be, using DCS instead of generic long writes.
> 
> Switching to transactions instead of using the atmel as a bridge also
> seems to resolve the sparkling pixels problem I've had.
> 
> Signed-off-by: Eric Anholt <eric@...olt.net>
> Fixes: 2f733d6194bd ("drm/panel: Add support for the Raspberry Pi 7" Touchscreen.")

Reviewed-by: Boris Brezillon <boris.brezillon@...tlin.com>

> ---
>  drivers/gpu/drm/panel/panel-raspberrypi-touchscreen.c | 14 +-------------
>  1 file changed, 1 insertion(+), 13 deletions(-)
> 
> diff --git a/drivers/gpu/drm/panel/panel-raspberrypi-touchscreen.c b/drivers/gpu/drm/panel/panel-raspberrypi-touchscreen.c
> index d964d454e4ae..2c9c9722734f 100644
> --- a/drivers/gpu/drm/panel/panel-raspberrypi-touchscreen.c
> +++ b/drivers/gpu/drm/panel/panel-raspberrypi-touchscreen.c
> @@ -238,12 +238,6 @@ static void rpi_touchscreen_i2c_write(struct rpi_touchscreen *ts,
>  
>  static int rpi_touchscreen_write(struct rpi_touchscreen *ts, u16 reg, u32 val)
>  {
> -#if 0
> -	/* The firmware uses LP DSI transactions like this to bring up
> -	 * the hardware, which should be faster than using I2C to then
> -	 * pass to the Toshiba.  However, I was unable to get it to
> -	 * work.
> -	 */
>  	u8 msg[] = {
>  		reg,
>  		reg >> 8,
> @@ -253,13 +247,7 @@ static int rpi_touchscreen_write(struct rpi_touchscreen *ts, u16 reg, u32 val)
>  		val >> 24,
>  	};
>  
> -	mipi_dsi_dcs_write_buffer(ts->dsi, msg, sizeof(msg));
> -#else
> -	rpi_touchscreen_i2c_write(ts, REG_WR_ADDRH, reg >> 8);
> -	rpi_touchscreen_i2c_write(ts, REG_WR_ADDRL, reg);
> -	rpi_touchscreen_i2c_write(ts, REG_WRITEH, val >> 8);
> -	rpi_touchscreen_i2c_write(ts, REG_WRITEL, val);
> -#endif
> +	mipi_dsi_generic_write(ts->dsi, msg, sizeof(msg));
>  
>  	return 0;
>  }



-- 
Boris Brezillon, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ