* Re: [PATCH v2] video: xilinxfb: Fix compilation warning
From: Geert Uytterhoeven @ 2013-07-25 13:36 UTC (permalink / raw)
To: Michal Simek
Cc: Jean-Christophe Plagniol-Villard, Jingoo Han, Michal Simek,
Tomi Valkeinen, Linux Fbdev development list,
linux-kernel@vger.kernel.org
In-Reply-To: <204d93f8a9dffef6ff00d961f91be0b465f21841.1374751310.git.michal.simek@xilinx.com>
On Thu, Jul 25, 2013 at 1:21 PM, Michal Simek <michal.simek@xilinx.com> wrote:
> regs_phys is phys_addr_t (u32 or u64).
> Lets retype it to u64.
This no longer matches the actual patch?
> Fixes compilation warning introduced by:
> video: xilinxfb: Use drvdata->regs_phys instead of physaddr
> (sha1: c88fafef0135e1e1c3e23c3e32ccbeeabc587f81)
>
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> ---
> Changes in v2:
> - Use %pa instead of casting
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply
* Re: [PATCH 2/2] video: imxfb: Add feature to setup PWM Contrast Control Register
From: Markus Pargmann @ 2013-07-25 13:38 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1374395709-20898-2-git-send-email-shc_work@mail.ru>
Hi,
On Sun, Jul 21, 2013 at 12:35:09PM +0400, Alexander Shiyan wrote:
> This patch adds feature to setup PWM Contrast Control Register.
> This register is used to control the signal output at the contrast pin,
> which controls contrast of the LCD panel.
http://www.spinics.net/lists/linux-fbdev/msg10002.html
Regards,
Markus
>
> Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
> ---
> Documentation/devicetree/bindings/video/fsl,imx-fb.txt | 1 +
> drivers/video/imxfb.c | 2 +-
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/video/fsl,imx-fb.txt b/Documentation/devicetree/bindings/video/fsl,imx-fb.txt
> index 46da08d..be10c65 100644
> --- a/Documentation/devicetree/bindings/video/fsl,imx-fb.txt
> +++ b/Documentation/devicetree/bindings/video/fsl,imx-fb.txt
> @@ -18,6 +18,7 @@ Optional properties:
> - fsl,dmacr: DMA Control Register value. This is optional. By default, the
> register is not modified as recommended by the datasheet.
> - fsl,lscr1: LCDC Sharp Configuration Register value.
> +- fsl,pwmr: LCDC PWM Contrast Control Register value.
>
> Example:
>
> diff --git a/drivers/video/imxfb.c b/drivers/video/imxfb.c
> index 8e104c4..d98299a 100644
> --- a/drivers/video/imxfb.c
> +++ b/drivers/video/imxfb.c
> @@ -806,8 +806,8 @@ static int imxfb_init_fbinfo(struct platform_device *pdev,
>
> fbi->lscr1 = IMXFB_LSCR1_DEFAULT;
> of_property_read_u32(np, "fsl,lscr1", &fbi->lscr1);
> -
> of_property_read_u32(np, "fsl,dmacr", &fbi->dmacr);
> + of_property_read_u32(np, "fsl,pwmr", &fbi->pwmr);
>
> /* These two function pointers could be used by some specific
> * platforms. */
> --
> 1.8.1.5
>
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
^ permalink raw reply
* Re: [PATCH v2] video: xilinxfb: Fix compilation warning
From: Michal Simek @ 2013-07-25 13:43 UTC (permalink / raw)
To: Geert Uytterhoeven
Cc: Michal Simek, Jean-Christophe Plagniol-Villard, Jingoo Han,
Tomi Valkeinen, Linux Fbdev development list,
linux-kernel@vger.kernel.org
In-Reply-To: <CAMuHMdX2mKANduZO9HaBHRZ13V0PztOc-uYxTymUsH8-NE5FEQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
On 07/25/2013 03:36 PM, Geert Uytterhoeven wrote:
> On Thu, Jul 25, 2013 at 1:21 PM, Michal Simek <michal.simek@xilinx.com> wrote:
>> regs_phys is phys_addr_t (u32 or u64).
>> Lets retype it to u64.
>
> This no longer matches the actual patch?
I need some holidays.
Will send v3.
Sorry,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
^ permalink raw reply
* [PATCH v3] video: xilinxfb: Fix compilation warning
From: Michal Simek @ 2013-07-25 13:45 UTC (permalink / raw)
To: Jean-Christophe Plagniol-Villard, Jingoo Han, Geert Uytterhoeven
Cc: Michal Simek, Tomi Valkeinen, linux-fbdev, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
regs_phys is phys_addr_t (u32 or u64).
Lets use %pa printk format specifier.
Fixes compilation warning introduced by:
video: xilinxfb: Use drvdata->regs_phys instead of physaddr
(sha1: c88fafef0135e1e1c3e23c3e32ccbeeabc587f81)
Signed-off-by: Michal Simek <michal.simek@xilinx.com>
---
Changes in v3:
- Fix commit message reported by Geert
Changes in v2:
- Use %pa instead of casting
ppc44x_defconfig
Fixes regressions in v3.11-rc2
---
drivers/video/xilinxfb.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/video/xilinxfb.c b/drivers/video/xilinxfb.c
index f3d4a69..6629b29 100644
--- a/drivers/video/xilinxfb.c
+++ b/drivers/video/xilinxfb.c
@@ -341,8 +341,8 @@ static int xilinxfb_assign(struct platform_device *pdev,
if (drvdata->flags & BUS_ACCESS_FLAG) {
/* Put a banner in the log (for DEBUG) */
- dev_dbg(dev, "regs: phys=%x, virt=%p\n", drvdata->regs_phys,
- drvdata->regs);
+ dev_dbg(dev, "regs: phys=%pa, virt=%p\n",
+ &drvdata->regs_phys, drvdata->regs);
}
/* Put a banner in the log (for DEBUG) */
dev_dbg(dev, "fb: phys=%llx, virt=%p, size=%x\n",
--
1.8.2.3
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply related
* Re: kmemleak warning in efifb_probe
From: Peter Jones @ 2013-07-25 15:47 UTC (permalink / raw)
To: Catalin Marinas
Cc: Alexandra N. Kossovsky, Jean-Christophe Plagniol-Villard,
Tomi Valkeinen, linux-fbdev, Linux Kernel Mailing List
In-Reply-To: <CAHkRjk4Ansh+Xr+cPQNacwx=aOb65_hW_MNRx5QVtatJCz5tqg@mail.gmail.com>
On Thu, Jul 25, 2013 at 01:18:31PM +0100, Catalin Marinas wrote:
> On 21 July 2013 16:11, Alexandra N. Kossovsky
> <Alexandra.Kossovsky@oktetlabs.ru> wrote:
> > I am running linux-3.10.0 with kmemleak and see following warnings
> > in /sys/kernel/debug/kmemleak:
> >
> > unreferenced object 0xffff880216fcfe00 (size 512):
> > comm "swapper/0", pid 1, jiffies 4294895429 (age 1415.320s)
> > hex dump (first 32 bytes):
> > 00 00 00 00 00 00 00 00 aa aa aa aa aa aa aa aa ................
> > 55 55 55 55 55 55 55 55 ff ff ff ff ff ff ff ff UUUUUUUU........
> > backtrace:
> > [<ffffffff813e415c>] kmemleak_alloc+0x21/0x3e
> > [<ffffffff8111c17f>] kmemleak_alloc_recursive.constprop.57+0x16/0x18
> > [<ffffffff8111e63b>] __kmalloc+0xf9/0x144
> > [<ffffffff8123d9cf>] fb_alloc_cmap_gfp+0x47/0xe1
> > [<ffffffff8123da77>] fb_alloc_cmap+0xe/0x10
> > [<ffffffff81aff40a>] efifb_probe+0x3e9/0x48f
> > [<ffffffff812c566f>] platform_drv_probe+0x34/0x5e
> > [<ffffffff812c3e6d>] driver_probe_device+0x98/0x1b4
> > [<ffffffff812c3fd7>] __driver_attach+0x4e/0x6f
> > [<ffffffff812c25bf>] bus_for_each_dev+0x57/0x8a
> > [<ffffffff812c3984>] driver_attach+0x19/0x1b
> > [<ffffffff812c362b>] bus_add_driver+0xde/0x201
> > [<ffffffff812c453f>] driver_register+0x8c/0x110
> > [<ffffffff812c510d>] platform_driver_register+0x41/0x43
> > [<ffffffff812c5127>] platform_driver_probe+0x18/0x8a
> > [<ffffffff81aff002>] efifb_init+0x276/0x295
>
> Does the efifb driver has any way to deallocate the cmap? I don't see
> any explicit call to fb_dealloc_cmap() apart from the error handling.
> My theory is that the efifb driver gets deregistered via
> do_remove_conflicting_framebuffers(). I'm not familiar with this code,
> just commenting from a kmemleak perspective.
You're right, that's the typical deregister path. I'll follow up with a
patch to test.
--
Peter
^ permalink raw reply
* [PATCH] Release efifb's colormap in efifb_destroy()
From: Peter Jones @ 2013-07-25 15:48 UTC (permalink / raw)
To: Catalin Marinas
Cc: Alexandra N. Kossovsky, linux-fbdev, linux-kernel, Peter Jones
In-Reply-To: <CAHkRjk4Ansh+Xr+cPQNacwx=aOb65_hW_MNRx5QVtatJCz5tqg@mail.gmail.com>
This was found by Alexandra Kossovsky, who noted this traceback from
kmemleak:
> unreferenced object 0xffff880216fcfe00 (size 512):
> comm "swapper/0", pid 1, jiffies 4294895429 (age 1415.320s)
> hex dump (first 32 bytes):
> 00 00 00 00 00 00 00 00 aa aa aa aa aa aa aa aa ................
> 55 55 55 55 55 55 55 55 ff ff ff ff ff ff ff ff UUUUUUUU........
> backtrace:
> [<ffffffff813e415c>] kmemleak_alloc+0x21/0x3e
> [<ffffffff8111c17f>]
> kmemleak_alloc_recursive.constprop.57+0x16/0x18
> [<ffffffff8111e63b>] __kmalloc+0xf9/0x144
> [<ffffffff8123d9cf>] fb_alloc_cmap_gfp+0x47/0xe1
> [<ffffffff8123da77>] fb_alloc_cmap+0xe/0x10
> [<ffffffff81aff40a>] efifb_probe+0x3e9/0x48f
> [<ffffffff812c566f>] platform_drv_probe+0x34/0x5e
> [<ffffffff812c3e6d>] driver_probe_device+0x98/0x1b4
> [<ffffffff812c3fd7>] __driver_attach+0x4e/0x6f
> [<ffffffff812c25bf>] bus_for_each_dev+0x57/0x8a
> [<ffffffff812c3984>] driver_attach+0x19/0x1b
> [<ffffffff812c362b>] bus_add_driver+0xde/0x201
> [<ffffffff812c453f>] driver_register+0x8c/0x110
> [<ffffffff812c510d>] platform_driver_register+0x41/0x43
> [<ffffffff812c5127>] platform_driver_probe+0x18/0x8a
> [<ffffffff81aff002>] efifb_init+0x276/0x295
---
drivers/video/efifb.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/video/efifb.c b/drivers/video/efifb.c
index 390b61b..1f3eab3 100644
--- a/drivers/video/efifb.c
+++ b/drivers/video/efifb.c
@@ -289,6 +289,7 @@ static void efifb_destroy(struct fb_info *info)
if (request_mem_succeeded)
release_mem_region(info->apertures->ranges[0].base,
info->apertures->ranges[0].size);
+ fb_dealloc_cmap(&info->cmap);
framebuffer_release(info);
}
--
1.8.3.1
^ permalink raw reply related
* [RFC 0/1] drm/pl111: Initial drm/kms driver for pl111
From: tom.cooksey @ 2013-07-25 17:17 UTC (permalink / raw)
To: dri-devel; +Cc: linux-fbdev, pawel.moll, linux-arm-kernel, Tom Cooksey
From: Tom Cooksey <tom.cooksey@arm.com>
Please find below the current state of our pl111 DRM/KMS driver. This
is lightly tested on a Versatile Express using X running the
xf86-video-armsoc DDX driver[i] with the patches applied to drm-next
as of ~last week. To actually see anything on the DVI output, you
must also apply Pawel Moll's VExpress DVI mux driver[ii] to select
the video signal from the ca9x4 core tile.
[i] <https://git.linaro.org/gitweb?p=arm/xorg/driver/xf86-video-armsoc.git;a=summary>
[ii] <https://patchwork.kernel.org/patch/1765981/>
Known issues:
* It uses KDS. We intend to switch to whatever implicit per-buffer
synchronisation mechanism gets merged, once something is merged.
* It abuses flags parameter of DRM_IOCTL_MODE_CREATE_DUMB to also
allocate buffers for the GPU. Still not sure how to resolve this
as we don't use DRM for our GPU driver.
* Doesn't handle page flip event sequence numbers and timestamps
* The v_sync handling needs work in general - a work queue is a
little overkill
* Doesn't support the import half of PRIME properly, only export
* Need to validate src rectangle size in
pl111_drm_cursor_plane_update()
* Only supports 640x480 mode, which is hard-coded. We intend to
rebase on top of CDF once it is merged, which hopefully will
handle a lot of the EDID parsing & mode setting for us (once
Pawel's CDF patches for VExpress also land).
I appreciate that's a fairly hefty list of known issues already!
However, we're waiting for both CDF & dma_buf sync mechanisms to land
before we can address some of those. So in the mean-time, I thought
someone might be interested in taking a look at what we have so far,
which is why I'm posting this now. Needless to say the code will need
to be refactored a fair bit, however I'm keen to get and additional
feedback anyone cares to give.
Cheers,
Tom
Tom Cooksey (1):
drm/pl111: Initial drm/kms driver for pl111 display controller
drivers/gpu/drm/Kconfig | 2 +
drivers/gpu/drm/Makefile | 1 +
drivers/gpu/drm/pl111/Kbuild | 14 +
drivers/gpu/drm/pl111/Kconfig | 9 +
drivers/gpu/drm/pl111/pl111_clcd_ext.h | 78 ++++
drivers/gpu/drm/pl111/pl111_drm.h | 227 ++++++++++++
drivers/gpu/drm/pl111/pl111_drm_connector.c | 166 +++++++++
drivers/gpu/drm/pl111/pl111_drm_crtc.c | 432 ++++++++++++++++++++++
drivers/gpu/drm/pl111/pl111_drm_cursor.c | 97 +++++
drivers/gpu/drm/pl111/pl111_drm_device.c | 319 +++++++++++++++++
drivers/gpu/drm/pl111/pl111_drm_dma_buf.c | 339 ++++++++++++++++++
drivers/gpu/drm/pl111/pl111_drm_encoder.c | 106 ++++++
drivers/gpu/drm/pl111/pl111_drm_fb.c | 152 ++++++++
drivers/gpu/drm/pl111/pl111_drm_funcs.h | 127 +++++++
drivers/gpu/drm/pl111/pl111_drm_gem.c | 287 +++++++++++++++
drivers/gpu/drm/pl111/pl111_drm_pl111.c | 513 +++++++++++++++++++++++++++
drivers/gpu/drm/pl111/pl111_drm_platform.c | 150 ++++++++
drivers/gpu/drm/pl111/pl111_drm_suspend.c | 35 ++
drivers/gpu/drm/pl111/pl111_drm_vma.c | 214 +++++++++++
19 files changed, 3268 insertions(+)
create mode 100644 drivers/gpu/drm/pl111/Kbuild
create mode 100644 drivers/gpu/drm/pl111/Kconfig
create mode 100644 drivers/gpu/drm/pl111/pl111_clcd_ext.h
create mode 100644 drivers/gpu/drm/pl111/pl111_drm.h
create mode 100644 drivers/gpu/drm/pl111/pl111_drm_connector.c
create mode 100644 drivers/gpu/drm/pl111/pl111_drm_crtc.c
create mode 100644 drivers/gpu/drm/pl111/pl111_drm_cursor.c
create mode 100644 drivers/gpu/drm/pl111/pl111_drm_device.c
create mode 100644 drivers/gpu/drm/pl111/pl111_drm_dma_buf.c
create mode 100644 drivers/gpu/drm/pl111/pl111_drm_encoder.c
create mode 100644 drivers/gpu/drm/pl111/pl111_drm_fb.c
create mode 100644 drivers/gpu/drm/pl111/pl111_drm_funcs.h
create mode 100644 drivers/gpu/drm/pl111/pl111_drm_gem.c
create mode 100644 drivers/gpu/drm/pl111/pl111_drm_pl111.c
create mode 100644 drivers/gpu/drm/pl111/pl111_drm_platform.c
create mode 100644 drivers/gpu/drm/pl111/pl111_drm_suspend.c
create mode 100644 drivers/gpu/drm/pl111/pl111_drm_vma.c
--
1.7.9.5
^ permalink raw reply
* Re: [PATCH 2/2] video: imxfb: Add feature to setup PWM Contrast Control Register
From: Alexander Shiyan @ 2013-07-25 17:20 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20130725133824.GD16871@s25.your-server.de>
On Thu, 25 Jul 2013 15:38:56 +0200
Markus Pargmann <mpa@pengutronix.de> wrote:
> Hi,
>
> On Sun, Jul 21, 2013 at 12:35:09PM +0400, Alexander Shiyan wrote:
> > This patch adds feature to setup PWM Contrast Control Register.
> > This register is used to control the signal output at the contrast pin,
> > which controls contrast of the LCD panel.
>
> http://www.spinics.net/lists/linux-fbdev/msg10002.html
PWM? I can not understand how the PWM driver will be connected to the
framebuffer driver. It is not backlight, this is contrast.
Even if we imagine that the driver will be connected through phandle,
then we will need to have at least 4! additional parameters in the framebuffer
driver: freq source, frequency and active pulse period + phandle to PWM.
Is it worth it, given that these parameters should not be adjustable?
On my opinion, the only one additional parameter in framebuffer is enough.
Thanks.
[...]
> > ---
> > Documentation/devicetree/bindings/video/fsl,imx-fb.txt | 1 +
> > drivers/video/imxfb.c | 2 +-
> > 2 files changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/Documentation/devicetree/bindings/video/fsl,imx-fb.txt b/Documentation/devicetree/bindings/video/fsl,imx-fb.txt
> > index 46da08d..be10c65 100644
> > --- a/Documentation/devicetree/bindings/video/fsl,imx-fb.txt
> > +++ b/Documentation/devicetree/bindings/video/fsl,imx-fb.txt
> > @@ -18,6 +18,7 @@ Optional properties:
> > - fsl,dmacr: DMA Control Register value. This is optional. By default, the
> > register is not modified as recommended by the datasheet.
> > - fsl,lscr1: LCDC Sharp Configuration Register value.
> > +- fsl,pwmr: LCDC PWM Contrast Control Register value.
> >
> > Example:
> >
> > diff --git a/drivers/video/imxfb.c b/drivers/video/imxfb.c
> > index 8e104c4..d98299a 100644
> > --- a/drivers/video/imxfb.c
> > +++ b/drivers/video/imxfb.c
> > @@ -806,8 +806,8 @@ static int imxfb_init_fbinfo(struct platform_device *pdev,
> >
> > fbi->lscr1 = IMXFB_LSCR1_DEFAULT;
> > of_property_read_u32(np, "fsl,lscr1", &fbi->lscr1);
> > -
> > of_property_read_u32(np, "fsl,dmacr", &fbi->dmacr);
> > + of_property_read_u32(np, "fsl,pwmr", &fbi->pwmr);
> >
> > /* These two function pointers could be used by some specific
> > * platforms. */
> > --
--
Alexander Shiyan <shc_work@mail.ru>
^ permalink raw reply
* Re: [RFC 0/1] drm/pl111: Initial drm/kms driver for pl111
From: Rob Clark @ 2013-07-25 18:21 UTC (permalink / raw)
To: tom.cooksey; +Cc: linux-arm-kernel, linux-fbdev, pawel.moll, dri-devel
In-Reply-To: <1374772648-19151-1-git-send-email-tom.cooksey@arm.com>
On Thu, Jul 25, 2013 at 1:17 PM, <tom.cooksey@arm.com> wrote:
> From: Tom Cooksey <tom.cooksey@arm.com>
>
> Please find below the current state of our pl111 DRM/KMS driver. This
> is lightly tested on a Versatile Express using X running the
> xf86-video-armsoc DDX driver[i] with the patches applied to drm-next
> as of ~last week. To actually see anything on the DVI output, you
> must also apply Pawel Moll's VExpress DVI mux driver[ii] to select
> the video signal from the ca9x4 core tile.
>
> [i] <https://git.linaro.org/gitweb?p=arm/xorg/driver/xf86-video-armsoc.git;a=summary>
> [ii] <https://patchwork.kernel.org/patch/1765981/>
>
>
> Known issues:
> * It uses KDS. We intend to switch to whatever implicit per-buffer
> synchronisation mechanism gets merged, once something is merged.
> * It abuses flags parameter of DRM_IOCTL_MODE_CREATE_DUMB to also
> allocate buffers for the GPU. Still not sure how to resolve this
> as we don't use DRM for our GPU driver.
any thoughts/plans about a DRM GPU driver? Ideally long term (esp.
once the dma-fence stuff is in place), we'd have gpu-specific drm
(gpu-only, no kms) driver, and SoC/display specific drm/kms driver,
using prime/dmabuf to share between the two.
> * Doesn't handle page flip event sequence numbers and timestamps
> * The v_sync handling needs work in general - a work queue is a
> little overkill
> * Doesn't support the import half of PRIME properly, only export
> * Need to validate src rectangle size in
> pl111_drm_cursor_plane_update()
> * Only supports 640x480 mode, which is hard-coded. We intend to
> rebase on top of CDF once it is merged, which hopefully will
> handle a lot of the EDID parsing & mode setting for us (once
> Pawel's CDF patches for VExpress also land).
note that drm core already handles EDID parsing quite nicely.. I'm not
entirely sure why CDF would be needed for this?
>
> I appreciate that's a fairly hefty list of known issues already!
> However, we're waiting for both CDF & dma_buf sync mechanisms to land
> before we can address some of those. So in the mean-time, I thought
> someone might be interested in taking a look at what we have so far,
> which is why I'm posting this now. Needless to say the code will need
> to be refactored a fair bit, however I'm keen to get and additional
> feedback anyone cares to give.
>
What is the dependency on CDF? Is there an external encoder/bridge
that could be shared between platforms?
btw, I think that having some share-able KMS objects is a good idea.
I'm not entirely sure that the directions that the current CDF
proposals are headed is necessarily the right way forward. I'd prefer
to see small/incremental evolution of KMS (ie. add drm_bridge and
drm_panel, and refactor the existing encoder-slave). Keeping it
inside drm means that we can evolve it more easily, and avoid layers
of glue code for no good reason.
BR,
-R
>
> Cheers,
>
> Tom
>
> Tom Cooksey (1):
> drm/pl111: Initial drm/kms driver for pl111 display controller
>
> drivers/gpu/drm/Kconfig | 2 +
> drivers/gpu/drm/Makefile | 1 +
> drivers/gpu/drm/pl111/Kbuild | 14 +
> drivers/gpu/drm/pl111/Kconfig | 9 +
> drivers/gpu/drm/pl111/pl111_clcd_ext.h | 78 ++++
> drivers/gpu/drm/pl111/pl111_drm.h | 227 ++++++++++++
> drivers/gpu/drm/pl111/pl111_drm_connector.c | 166 +++++++++
> drivers/gpu/drm/pl111/pl111_drm_crtc.c | 432 ++++++++++++++++++++++
> drivers/gpu/drm/pl111/pl111_drm_cursor.c | 97 +++++
> drivers/gpu/drm/pl111/pl111_drm_device.c | 319 +++++++++++++++++
> drivers/gpu/drm/pl111/pl111_drm_dma_buf.c | 339 ++++++++++++++++++
> drivers/gpu/drm/pl111/pl111_drm_encoder.c | 106 ++++++
> drivers/gpu/drm/pl111/pl111_drm_fb.c | 152 ++++++++
> drivers/gpu/drm/pl111/pl111_drm_funcs.h | 127 +++++++
> drivers/gpu/drm/pl111/pl111_drm_gem.c | 287 +++++++++++++++
> drivers/gpu/drm/pl111/pl111_drm_pl111.c | 513 +++++++++++++++++++++++++++
> drivers/gpu/drm/pl111/pl111_drm_platform.c | 150 ++++++++
> drivers/gpu/drm/pl111/pl111_drm_suspend.c | 35 ++
> drivers/gpu/drm/pl111/pl111_drm_vma.c | 214 +++++++++++
> 19 files changed, 3268 insertions(+)
> create mode 100644 drivers/gpu/drm/pl111/Kbuild
> create mode 100644 drivers/gpu/drm/pl111/Kconfig
> create mode 100644 drivers/gpu/drm/pl111/pl111_clcd_ext.h
> create mode 100644 drivers/gpu/drm/pl111/pl111_drm.h
> create mode 100644 drivers/gpu/drm/pl111/pl111_drm_connector.c
> create mode 100644 drivers/gpu/drm/pl111/pl111_drm_crtc.c
> create mode 100644 drivers/gpu/drm/pl111/pl111_drm_cursor.c
> create mode 100644 drivers/gpu/drm/pl111/pl111_drm_device.c
> create mode 100644 drivers/gpu/drm/pl111/pl111_drm_dma_buf.c
> create mode 100644 drivers/gpu/drm/pl111/pl111_drm_encoder.c
> create mode 100644 drivers/gpu/drm/pl111/pl111_drm_fb.c
> create mode 100644 drivers/gpu/drm/pl111/pl111_drm_funcs.h
> create mode 100644 drivers/gpu/drm/pl111/pl111_drm_gem.c
> create mode 100644 drivers/gpu/drm/pl111/pl111_drm_pl111.c
> create mode 100644 drivers/gpu/drm/pl111/pl111_drm_platform.c
> create mode 100644 drivers/gpu/drm/pl111/pl111_drm_suspend.c
> create mode 100644 drivers/gpu/drm/pl111/pl111_drm_vma.c
>
> --
> 1.7.9.5
>
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply
* Re: [PATCH v3] video: xilinxfb: Fix compilation warning
From: Jingoo Han @ 2013-07-25 23:14 UTC (permalink / raw)
To: 'Michal Simek',
'Jean-Christophe Plagniol-Villard'
Cc: 'Michal Simek', 'Tomi Valkeinen', linux-fbdev,
linux-kernel, 'Geert Uytterhoeven', Jingoo Han
In-Reply-To: <b8701d73538d37495b41ef465440a6d5f3018870.1374759923.git.michal.simek@xilinx.com>
On Thursday, July 25, 2013 10:45 PM, Michal Simek wrote:
>
> regs_phys is phys_addr_t (u32 or u64).
> Lets use %pa printk format specifier.
>
> Fixes compilation warning introduced by:
> video: xilinxfb: Use drvdata->regs_phys instead of physaddr
> (sha1: c88fafef0135e1e1c3e23c3e32ccbeeabc587f81)
>
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
It looks good.
Reviewed-by: Jingoo Han <jg1.han@samsung.com>
Best regards,
Jingoo Han
> ---
> Changes in v3:
> - Fix commit message reported by Geert
>
> Changes in v2:
> - Use %pa instead of casting
>
> ppc44x_defconfig
> Fixes regressions in v3.11-rc2
>
> ---
> drivers/video/xilinxfb.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/video/xilinxfb.c b/drivers/video/xilinxfb.c
> index f3d4a69..6629b29 100644
> --- a/drivers/video/xilinxfb.c
> +++ b/drivers/video/xilinxfb.c
> @@ -341,8 +341,8 @@ static int xilinxfb_assign(struct platform_device *pdev,
>
> if (drvdata->flags & BUS_ACCESS_FLAG) {
> /* Put a banner in the log (for DEBUG) */
> - dev_dbg(dev, "regs: phys=%x, virt=%p\n", drvdata->regs_phys,
> - drvdata->regs);
> + dev_dbg(dev, "regs: phys=%pa, virt=%p\n",
> + &drvdata->regs_phys, drvdata->regs);
> }
> /* Put a banner in the log (for DEBUG) */
> dev_dbg(dev, "fb: phys=%llx, virt=%p, size=%x\n",
> --
> 1.8.2.3
>
^ permalink raw reply
* Re: [PATCHv2 2/3] video: hx8357: Make IM pins optional
From: Jingoo Han @ 2013-07-25 23:47 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1374757513-2253-3-git-send-email-maxime.ripard@free-electrons.com>
On Thursday, July 25, 2013 10:05 PM, Maxime Ripard wrote:
>
> The IM pins of the HX8357 controller are used to define the interface
> used to feed pixel stream to the LCD panel.
>
> Most of the time, these pins are directly routed to either the ground or
> the VCC to set their values.
>
> Remove the need to assign GPIOs to these pins when we are in such a case.
>
> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
> ---
> drivers/video/backlight/hx8357.c | 53 +++++++++++++++++++++++-----------------
> 1 file changed, 31 insertions(+), 22 deletions(-)
>
[.....]
> + if (of_find_property(spi->dev.of_node, "im-gpios", NULL)) {
> + lcd->use_im_pins = 1;
> +
> + for (i = 0; i < HX8357_NUM_IM_PINS; i++) {
> + lcd->im_pins[i] = of_get_named_gpio(spi->dev.of_node,
> + "im-gpios", i);
> + if (lcd->im_pins[i] = -EPROBE_DEFER) {
> + dev_info(&spi->dev, "GPIO requested is not here yet, deferring the
> probe\n");
> + return -EPROBE_DEFER;
> + }
> + if (!gpio_is_valid(lcd->im_pins[i])) {
> + dev_err(&spi->dev, "Missing dt property: im-gpios\n");
> + return -EINVAL;
> + }
> +
> + ret = devm_gpio_request_one(&spi->dev, lcd->im_pins[i],
> + GPIOF_OUT_INIT_LOW,
> + "im_pins");
> + if (ret) {
> + dev_err(&spi->dev, "failed to request gpio %d: %d\n",
> + lcd->im_pins[i], ret);
> + return -EINVAL;
> + }
> }
> -
> - ret = devm_gpio_request_one(&spi->dev, lcd->im_pins[i],
> - GPIOF_OUT_INIT_LOW, "im_pins");
> - if (ret) {
> - dev_err(&spi->dev, "failed to request gpio %d: %d\n",
> - lcd->im_pins[i], ret);
> - return -EINVAL;
> - }
> - }
> + } else
> + lcd->use_im_pins = 0;
According to the 'Documentation/CodingStyle', braces are necessary as below.
} else {
lcd->use_im_pins = 0;
}
Others look good.
Acked-by: Jingoo Han <jg1.han@samsung.com>
Best regards,
Jingoo Han
^ permalink raw reply
* Re: [PATCHv2 3/3] fb: backlight: HX8357: Add HX8369 support
From: Jingoo Han @ 2013-07-25 23:52 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1374757513-2253-4-git-send-email-maxime.ripard@free-electrons.com>
On Thursday, July 25, 2013 10:05 PM, Maxime Ripard wrote:
>
> From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>
> Add support for the Himax HX8369 controller as it is quite similar to the
> hx8357.
>
> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
> Acked-by: Jingoo Han <jg1.han@samsung.com>
> ---
> drivers/video/backlight/hx8357.c | 221 ++++++++++++++++++++++++++++++++++++---
> 1 file changed, 206 insertions(+), 15 deletions(-)
>
[....]
> + ret = hx8357_spi_write_byte(lcdev, HX8357_SET_DISPLAY_ON);
> + if (ret < 0)
> + return ret;
> +
> + msleep(100);
Hi Maxime Ripard,
Could you add comment on this huge delay, too?
Best regards,
Jingoo Han
^ permalink raw reply
* Re: [PATCH] vga16fb: Remove unused variable
From: Tomi Valkeinen @ 2013-07-26 7:30 UTC (permalink / raw)
To: Luis Henriques
Cc: linux-fbdev, Jean-Christophe Plagniol-Villard, linux-kernel
In-Reply-To: <20130710225659.GA14107@hercules>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
On 11/07/13 01:57, Luis Henriques wrote:
> Fix build warning of unused variable:
>
> drivers/video/vga16fb.c:1268:26: warning: unused variable ‘dev’ [-Wunused-variable]
>
> Signed-off-by: Luis Henriques<luis.henriques@canonical.com>
> ---
> drivers/video/vga16fb.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/video/vga16fb.c b/drivers/video/vga16fb.c
> index 830ded4..2827333 100644
> --- a/drivers/video/vga16fb.c
> +++ b/drivers/video/vga16fb.c
> @@ -1265,7 +1265,6 @@ static void vga16fb_imageblit(struct fb_info *info, const struct fb_image *image
>
> static void vga16fb_destroy(struct fb_info *info)
> {
> - struct platform_device *dev = container_of(info->device, struct platform_device, dev);
> iounmap(info->screen_base);
> fb_dealloc_cmap(&info->cmap);
> /* XXX unshare VGA regions */
>
Thanks, I've applied this into my 3.12/fbdev branch.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
^ permalink raw reply
* Re: [PATCH V2] driver/vga16fb.c: remove the unused variable "dev" of function vga16fb_destroy()
From: Tomi Valkeinen @ 2013-07-26 7:31 UTC (permalink / raw)
To: Paul Bolle
Cc: Geert Uytterhoeven, Gu Zheng, Jean-Christophe PLAGNIOL-VILLARD,
Linux Fbdev development list, linux-kernel
In-Reply-To: <1374747739.29835.45.camel@x61.thuisdomein>
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
On 25/07/13 13:22, Paul Bolle wrote:
> On Thu, 2013-07-25 at 12:11 +0200, Geert Uytterhoeven wrote:
>> Please send a v3, which has the version info under the above "---",
>> instead of making it a part of the patch description to be committed.
>
> Grepping through my mail tells me this is the fourth time a patch has
> been submitted to fix this trivial issue. Perhaps (one of) the
> maintainers can indicate which patch, if any, the maintainers have taken
> or will be taking.
I took the the oldest patch for this in my mailbox, from Luis.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
^ permalink raw reply
* Re: [PATCH v3] video: xilinxfb: Fix compilation warning
From: Tomi Valkeinen @ 2013-07-26 7:33 UTC (permalink / raw)
To: Michal Simek
Cc: Jean-Christophe Plagniol-Villard, Jingoo Han, Geert Uytterhoeven,
Michal Simek, linux-fbdev, linux-kernel
In-Reply-To: <b8701d73538d37495b41ef465440a6d5f3018870.1374759923.git.michal.simek@xilinx.com>
[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]
On 25/07/13 16:45, Michal Simek wrote:
> regs_phys is phys_addr_t (u32 or u64).
> Lets use %pa printk format specifier.
>
> Fixes compilation warning introduced by:
> video: xilinxfb: Use drvdata->regs_phys instead of physaddr
> (sha1: c88fafef0135e1e1c3e23c3e32ccbeeabc587f81)
>
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> ---
> Changes in v3:
> - Fix commit message reported by Geert
>
> Changes in v2:
> - Use %pa instead of casting
>
> ppc44x_defconfig
> Fixes regressions in v3.11-rc2
>
> ---
> drivers/video/xilinxfb.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/video/xilinxfb.c b/drivers/video/xilinxfb.c
> index f3d4a69..6629b29 100644
> --- a/drivers/video/xilinxfb.c
> +++ b/drivers/video/xilinxfb.c
> @@ -341,8 +341,8 @@ static int xilinxfb_assign(struct platform_device *pdev,
>
> if (drvdata->flags & BUS_ACCESS_FLAG) {
> /* Put a banner in the log (for DEBUG) */
> - dev_dbg(dev, "regs: phys=%x, virt=%p\n", drvdata->regs_phys,
> - drvdata->regs);
> + dev_dbg(dev, "regs: phys=%pa, virt=%p\n",
> + &drvdata->regs_phys, drvdata->regs);
> }
> /* Put a banner in the log (for DEBUG) */
> dev_dbg(dev, "fb: phys=%llx, virt=%p, size=%x\n",
> --
> 1.8.2.3
>
Thanks, I've applied this into my 3.12/fbdev branch.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
^ permalink raw reply
* Re: [PATCH v3] video: xilinxfb: Fix compilation warning
From: Tomi Valkeinen @ 2013-07-26 7:35 UTC (permalink / raw)
To: Michal Simek
Cc: Jean-Christophe Plagniol-Villard, Jingoo Han, Geert Uytterhoeven,
Michal Simek, linux-fbdev, linux-kernel
In-Reply-To: <51F2262F.1020203@ti.com>
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
On 26/07/13 10:33, Tomi Valkeinen wrote:
> On 25/07/13 16:45, Michal Simek wrote:
>> regs_phys is phys_addr_t (u32 or u64).
>> Lets use %pa printk format specifier.
>>
>> Fixes compilation warning introduced by:
>> video: xilinxfb: Use drvdata->regs_phys instead of physaddr
>> (sha1: c88fafef0135e1e1c3e23c3e32ccbeeabc587f81)
>>
>> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> Thanks, I've applied this into my 3.12/fbdev branch.
Actually, let's put this into 3.11-fixes/fbdev branch.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
^ permalink raw reply
* Re: [PATCH 2/2] video: imxfb: Add feature to setup PWM Contrast Control Register
From: Sascha Hauer @ 2013-07-26 7:38 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20130725212053.b39198a8610efc157a91b7be@mail.ru>
On Thu, Jul 25, 2013 at 09:20:53PM +0400, Alexander Shiyan wrote:
> On Thu, 25 Jul 2013 15:38:56 +0200
> Markus Pargmann <mpa@pengutronix.de> wrote:
>
> > Hi,
> >
> > On Sun, Jul 21, 2013 at 12:35:09PM +0400, Alexander Shiyan wrote:
> > > This patch adds feature to setup PWM Contrast Control Register.
> > > This register is used to control the signal output at the contrast pin,
> > > which controls contrast of the LCD panel.
> >
> > http://www.spinics.net/lists/linux-fbdev/msg10002.html
>
> PWM? I can not understand how the PWM driver will be connected to the
> framebuffer driver. It is not backlight, this is contrast.
> Even if we imagine that the driver will be connected through phandle,
> then we will need to have at least 4! additional parameters in the framebuffer
> driver: freq source, frequency and active pulse period + phandle to PWM.
> Is it worth it, given that these parameters should not be adjustable?
> On my opinion, the only one additional parameter in framebuffer is enough.
> Thanks.
Why should the contrast of a display not be adjustable?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
^ permalink raw reply
* Re: [PATCH RESEND] video: mxsfb: Let device core handle pinctrl
From: Tomi Valkeinen @ 2013-07-26 7:46 UTC (permalink / raw)
To: linux-fbdev
In-Reply-To: <1373923884-13332-1-git-send-email-festevam@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 477 bytes --]
On 16/07/13 00:31, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> Since commit ab78029 (drivers/pinctrl: grab default handles from device core)
> we can rely on device core for handling pinctrl, so remove
> devm_pinctrl_get_select_default() from the driver.
>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> Acked-by: Shawn Guo <shawn.guo@linaro.org>
Thanks, I've applied this into my 3.12/fbdev branch.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
^ permalink raw reply
* Re: [PATCH] video: nuc900fb: fix to pass correct device identity to request_irq()
From: Tomi Valkeinen @ 2013-07-26 7:57 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <CAPgLHd9CZ=VponJTbTGKTXVTdvMQM6_T+-RWuPMrk0WYZPbW1Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
On 16/07/13 03:07, Wei Yongjun wrote:
> The IRQ handler nuc900fb_irqhandler() use dev_id as a type of
> struct nuc900fb_info *, so we should pass fbi as the device
> identity to request_irq().
>
> Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
> ---
> Was 'video: nuc900fb: fix to pass correct device identity to free_irq()'
> ---
> drivers/video/nuc900fb.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/video/nuc900fb.c b/drivers/video/nuc900fb.c
> index 8c527e5..796e511 100644
> --- a/drivers/video/nuc900fb.c
> +++ b/drivers/video/nuc900fb.c
> @@ -587,8 +587,7 @@ static int nuc900fb_probe(struct platform_device *pdev)
> fbinfo->flags = FBINFO_FLAG_DEFAULT;
> fbinfo->pseudo_palette = &fbi->pseudo_pal;
>
> - ret = request_irq(irq, nuc900fb_irqhandler, 0,
> - pdev->name, fbinfo);
> + ret = request_irq(irq, nuc900fb_irqhandler, 0, pdev->name, fbi);
> if (ret) {
> dev_err(&pdev->dev, "cannot register irq handler %d -err %d\n",
> irq, ret);
>
Thanks, I've applied this into my 3.11-fixes/fbdev branch.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
^ permalink raw reply
* Re: [PATCH 2/2] video: imxfb: Add feature to =?UTF-8?B?c2V0dXAgUFdNIENvb
From: Alexander Shiyan @ 2013-07-26 7:59 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20130726073848.GF2737@pengutronix.de>
PiBPbiBUaHUsIEp1bCAyNSwgMjAxMyBhdCAwOToyMDo1M1BNICswNDAwLCBBbGV4YW5kZXIgU2hp
eWFuIHdyb3RlOgo+ID4gT24gVGh1LCAyNSBKdWwgMjAxMyAxNTozODo1NiArMDIwMAo+ID4gTWFy
a3VzIFBhcmdtYW5uIDxtcGFAcGVuZ3V0cm9uaXguZGU+IHdyb3RlOgo+ID4gCj4gPiA+IEhpLAo+
ID4gPiAKPiA+ID4gT24gU3VuLCBKdWwgMjEsIDIwMTMgYXQgMTI6MzU6MDlQTSArMDQwMCwgQWxl
eGFuZGVyIFNoaXlhbiB3cm90ZToKPiA+ID4gPiBUaGlzIHBhdGNoIGFkZHMgZmVhdHVyZSB0byBz
ZXR1cCBQV00gQ29udHJhc3QgQ29udHJvbCBSZWdpc3Rlci4KPiA+ID4gPiBUaGlzIHJlZ2lzdGVy
IGlzIHVzZWQgdG8gY29udHJvbCB0aGUgc2lnbmFsIG91dHB1dCBhdCB0aGUgY29udHJhc3QgcGlu
LAo+ID4gPiA+IHdoaWNoIGNvbnRyb2xzIGNvbnRyYXN0IG9mIHRoZSBMQ0QgcGFuZWwuCj4gPiA+
IAo+ID4gPiBodHRwOi8vd3d3LnNwaW5pY3MubmV0L2xpc3RzL2xpbnV4LWZiZGV2L21zZzEwMDAy
Lmh0bWwKPiA+IAo+ID4gUFdNPyBJIGNhbiBub3QgdW5kZXJzdGFuZCBob3cgdGhlIFBXTSBkcml2
ZXIgd2lsbCBiZSBjb25uZWN0ZWQgdG8gdGhlCj4gPiBmcmFtZWJ1ZmZlciBkcml2ZXIuIEl0IGlz
IG5vdCBiYWNrbGlnaHQsIHRoaXMgaXMgY29udHJhc3QuCj4gPiBFdmVuIGlmIHdlIGltYWdpbmUg
dGhhdCB0aGUgZHJpdmVyIHdpbGwgYmUgY29ubmVjdGVkIHRocm91Z2ggcGhhbmRsZSwKPiA+IHRo
ZW4gd2Ugd2lsbCBuZWVkIHRvIGhhdmUgYXQgbGVhc3QgNCEgYWRkaXRpb25hbCBwYXJhbWV0ZXJz
IGluIHRoZSBmcmFtZWJ1ZmZlcgo+ID4gZHJpdmVyOiBmcmVxIHNvdXJjZSwgZnJlcXVlbmN5IGFu
ZCBhY3RpdmUgcHVsc2UgcGVyaW9kICsgcGhhbmRsZSB0byBQV00uCj4gPiBJcyBpdCB3b3J0aCBp
dCwgZ2l2ZW4gdGhhdCB0aGVzZSBwYXJhbWV0ZXJzIHNob3VsZCBub3QgYmUgYWRqdXN0YWJsZT8K
PiA+IE9uIG15IG9waW5pb24sIHRoZSBvbmx5IG9uZSBhZGRpdGlvbmFsIHBhcmFtZXRlciBpbiBm
cmFtZWJ1ZmZlciBpcyBlbm91Z2guCj4gPiBUaGFua3MuCj4gCj4gV2h5IHNob3VsZCB0aGUgY29u
dHJhc3Qgb2YgYSBkaXNwbGF5IG5vdCBiZSBhZGp1c3RhYmxlPwoKSSBzdGlsbCBjYW4gbm90IHVu
ZGVyc3RhbmQgdGhlIGludGVyZmFjZSB0aHJvdWdoIHdoaWNoIGl0IGNhbiBiZSBjaGFuZ2VkLgpT
YW1lIGFzIGhvdyB0aGUgZGVmYXVsdCBzZXR0aW5ncyBjYW4gYmUgcGFzc2VkIHRvIHRoZSBmcmFt
ZWJ1ZmZlciBkcml2ZXIuCgotLS0K
^ permalink raw reply
* Re: [PATCH v3] video: xilinxfb: Fix compilation warning
From: Michal Simek @ 2013-07-26 8:27 UTC (permalink / raw)
To: Tomi Valkeinen
Cc: Michal Simek, Jean-Christophe Plagniol-Villard, Jingoo Han,
Geert Uytterhoeven, linux-fbdev, linux-kernel
In-Reply-To: <51F226C2.9000206@ti.com>
[-- Attachment #1: Type: text/plain, Size: 911 bytes --]
On 07/26/2013 09:35 AM, Tomi Valkeinen wrote:
> On 26/07/13 10:33, Tomi Valkeinen wrote:
>> On 25/07/13 16:45, Michal Simek wrote:
>>> regs_phys is phys_addr_t (u32 or u64).
>>> Lets use %pa printk format specifier.
>>>
>>> Fixes compilation warning introduced by:
>>> video: xilinxfb: Use drvdata->regs_phys instead of physaddr
>>> (sha1: c88fafef0135e1e1c3e23c3e32ccbeeabc587f81)
>>>
>>> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
>
>> Thanks, I've applied this into my 3.12/fbdev branch.
>
> Actually, let's put this into 3.11-fixes/fbdev branch.
>
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
^ permalink raw reply
* Re: [patch -next] fb: fix recent breakage in correct_chipset()
From: Tomi Valkeinen @ 2013-07-26 8:34 UTC (permalink / raw)
To: linux-fbdev
In-Reply-To: <20130702062821.GC24410@elgon.mountain>
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
On 02/07/13 09:28, Dan Carpenter wrote:
> The 6e36308a6f "fb: fix atyfb build warning" isn't right. It makes all
> the indexes off by one. This patch reverts it and casts the
> ARRAY_SIZE() to int to silence the build warning.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> diff --git a/drivers/video/aty/atyfb_base.c b/drivers/video/aty/atyfb_base.c
> index a89c15d..9b0f12c 100644
> --- a/drivers/video/aty/atyfb_base.c
> +++ b/drivers/video/aty/atyfb_base.c
> @@ -435,8 +435,8 @@ static int correct_chipset(struct atyfb_par *par)
> const char *name;
> int i;
>
> - for (i = ARRAY_SIZE(aty_chips); i > 0; i--)
> - if (par->pci_id == aty_chips[i - 1].pci_id)
> + for (i = (int)ARRAY_SIZE(aty_chips) - 1; i >= 0; i--)
> + if (par->pci_id == aty_chips[i].pci_id)
> break;
>
> if (i < 0)
>
Thanks, I've applied this into my 3.11-fixes/fbdev branch.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
^ permalink raw reply
* Re: [PATCH] matroxfb: replace kmalloc and memset with kzalloc.
From: Tomi Valkeinen @ 2013-07-26 8:36 UTC (permalink / raw)
To: Alexandru Juncu; +Cc: plagnioj, linux-fbdev, linux-kernel
In-Reply-To: <1373637618-10529-1-git-send-email-alexj@rosedu.org>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
On 12/07/13 17:00, Alexandru Juncu wrote:
> Signed-off-by: Alexandru Juncu <alexj@rosedu.org>
> ---
> drivers/video/matrox/matroxfb_base.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/video/matrox/matroxfb_base.c b/drivers/video/matrox/matroxfb_base.c
> index 401a56e..2456529 100644
> --- a/drivers/video/matrox/matroxfb_base.c
> +++ b/drivers/video/matrox/matroxfb_base.c
> @@ -2029,10 +2029,9 @@ static int matroxfb_probe(struct pci_dev* pdev, const struct pci_device_id* dumm
> return -1;
> }
>
> - minfo = kmalloc(sizeof(*minfo), GFP_KERNEL);
> + minfo = kzalloc(sizeof(*minfo), GFP_KERNEL);
> if (!minfo)
> return -1;
> - memset(minfo, 0, sizeof(*minfo));
>
> minfo->pcidev = pdev;
> minfo->dead = 0;
>
Thanks, I've applied this into my 3.12/fbdev branch.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
^ permalink raw reply
* Re: [PATCH] video: sh7760fb: fix to pass correct device identity to free_irq()
From: Tomi Valkeinen @ 2013-07-26 8:38 UTC (permalink / raw)
To: linux-fbdev
In-Reply-To: <CAPgLHd9+d0Csf0kad8fnYQc4UQLdoJCo+-MZNNGKi_PTxeBJjQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
On 12/07/13 16:20, Wei Yongjun wrote:
> From: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
>
> free_irq() expects the same device identity that was passed to
> corresponding request_irq(), otherwise the IRQ is not freed.
>
> Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
> ---
> drivers/video/sh7760fb.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/video/sh7760fb.c b/drivers/video/sh7760fb.c
> index a8c6c43..1265b25 100644
> --- a/drivers/video/sh7760fb.c
> +++ b/drivers/video/sh7760fb.c
> @@ -567,7 +567,7 @@ static int sh7760fb_remove(struct platform_device *dev)
> fb_dealloc_cmap(&info->cmap);
> sh7760fb_free_mem(info);
> if (par->irq >= 0)
> - free_irq(par->irq, par);
> + free_irq(par->irq, &par->vsync);
> iounmap(par->base);
> release_mem_region(par->ioarea->start, resource_size(par->ioarea));
> framebuffer_release(info);
>
Thanks, I've applied this into my 3.11-fixes/fbdev branch.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
^ permalink raw reply
* Re: [PATCH] drivers/video: remove unused parameter in Kconfig
From: Tomi Valkeinen @ 2013-07-26 8:41 UTC (permalink / raw)
To: Michael Opdenacker; +Cc: plagnioj, linux-fbdev, linux-kernel
In-Reply-To: <1373259806-23067-1-git-send-email-michael.opdenacker@free-electrons.com>
[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]
On 08/07/13 08:03, Michael Opdenacker wrote:
> This patch proposes to remove the FB_NUC900_DEBUG kernel configuration
> parameter defined in drivers/video/Kconfig, but used nowhere
> in the makefiles and source code.
>
> Signed-off-by: Michael Opdenacker <michael.opdenacker@free-electrons.com>
> ---
> drivers/video/Kconfig | 7 -------
> 1 file changed, 7 deletions(-)
>
> diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig
> index 2e937bd..a9c0964 100644
> --- a/drivers/video/Kconfig
> +++ b/drivers/video/Kconfig
> @@ -2098,13 +2098,6 @@ config GPM1040A0_320X240
> bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
> depends on FB_NUC900
>
> -config FB_NUC900_DEBUG
> - bool "NUC900 lcd debug messages"
> - depends on FB_NUC900
> - help
> - Turn on debugging messages. Note that you can set/unset at run time
> - through sysfs
> -
> config FB_SM501
> tristate "Silicon Motion SM501 framebuffer support"
> depends on FB && MFD_SM501
>
Thanks, I've applied this into my 3.12/fbdev branch.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox