On Thu, Apr 21, 2016 at 02:11:19PM +0200, Holger Schurig wrote:
> Thierry Reding writes:
> > Applied, thanks.
>
> I once read that this is the recommended way to go, instead of
> specifying the timings in the device tree. Why is this so? Any new
> display just increases the .text size of the ker
Thierry Reding writes:
> Applied, thanks.
I once read that this is the recommended way to go, instead of
specifying the timings in the device tree. Why is this so? Any new
display just increases the .text size of the kernel unnessary.
Did this idea stem from the era where bootloaders like Bareb
On Wed, Apr 20, 2016 at 03:37:15PM +0200, Boris Brezillon wrote:
> From: Riccardo Bortolato
>
> Add support for the Innolux AT070TN92 panel.
>
> Signed-off-by: Riccardo Bortolato
> Signed-off-by: Boris Brezillon
>
> ---
> Changes since v1:
> - Add missing SoB
> ---
> .../bindings/display/pan
From: Riccardo Bortolato
Add support for the Innolux AT070TN92 panel.
Signed-off-by: Riccardo Bortolato
Signed-off-by: Boris Brezillon
---
Changes since v1:
- Add missing SoB
---
.../bindings/display/panel/innolux,at070tn92.txt | 7 ++
drivers/gpu/drm/panel/panel-simple.c
4 matches
Mail list logo