From: Markus Elfring
Date: Fri, 23 Sep 2016 18:24:32 +0200
A few update suggestions were taken into account
from static source code analysis.
Markus Elfring (3):
Use kmalloc_array() in vmw_surface_define_ioctl()
Use memdup_user() rather than duplicating its implementation
Adjust checks for
From: Markus Elfring
Date: Thu, 22 Sep 2016 21:54:33 +0200
Multiplications for the size determination of memory allocations
indicated that array data structures should be processed.
Thus use the corresponding function "kmalloc_array".
This issue was detected by using the Coccinelle software.
Si
From: Markus Elfring
Date: Fri, 23 Sep 2016 17:26:02 +0200
* Reuse existing functionality from memdup_user() instead of keeping
duplicate source code.
* Try this copy operation before allocating memory for the data structure
member "offsets".
* Delete the local variable "user_sizes" which b
From: Markus Elfring
Date: Fri, 23 Sep 2016 17:53:49 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
The script "checkpatch.pl" can point information out like the following.
Comparison to NULL could be written !â¦
Thus fix the affected source cod
https://bugzilla.kernel.org/show_bug.cgi?id=172421
--- Comment #16 from Christian König ---
(In reply to Roland Scheidegger from comment #15)
> Oh interesting - didn't know voltage was directly tied to clock frequency
> here. Makes sense then to not allow it (at least if that circuitry isn't
> s
On Sat, Sep 17, 2016 at 11:34:22AM +0200, Peter Rosin wrote:
> From: Gustaf Lindström
>
> The Sharp 15" LQ150X1LG11 panel is an XGA TFT LCD panel.
>
> Signed-off-by: Gustaf Lindström
> Signed-off-by: Peter Rosin
> ---
> .../bindings/display/panel/sharp,lq150x1lg11.txt | 7 ++
> drive
Am 23.09.2016 um 17:20 schrieb Chris Wilson:
> On Fri, Sep 23, 2016 at 03:50:44PM +0200, Daniel Vetter wrote:
>> On Mon, Aug 29, 2016 at 08:08:34AM +0100, Chris Wilson wrote:
>>> Currently we install a callback for performing poll on a dma-buf,
>>> irrespective of the timeout. This involves taking
On Tue, Sep 20, 2016 at 03:02:51AM +0800, Randy Li wrote:
> The Chunghwa CLAA070WP03XG is a 7" 1280x800 panel, which can be
> supported by the simple panel driver.
>
> Signed-off-by: Randy Li
> ---
> .../display/panel/chunghwa,claa070wp03xg.txt | 7 ++
> drivers/gpu/drm/panel/panel-si
On Thu, Sep 22, 2016 at 01:35:24PM +0300, Peter Ujfalusi wrote:
> There are display panels which demands that the sync signal is driven on
> different edge than the pixel data.
> With the syncclk-active property we can specify the clk edge to be used to
> drive the sync signal. When the property is
Since commit 62336cc1ca1b96f33e3344ca6e910d30adca749a adev is now no
longer required in amdgpu_drv.c
Signed-off-by: Mike Lothian
---
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
b/drivers/gpu/drm/amd/amdgpu/am
t; * torn down properly on reboot/shutdown.
> --
> 2.10.0
>
>
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160923/8c1be32d/attachment.html>
Since commit 62336cc1ca1b96f33e3344ca6e910d30adca749a the variables adev
and dev are no longer required
Signed-off-by: Mike Lothian
---
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
b/drivers/gpu/drm/amd/amd
ttachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160923/a1cfcba6/attachment.html>
nee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160923/8c492fec/attachment-0001.html>
the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160923/ded228b2/attachment.html>
On Fri, Sep 23, 2016 at 4:39 PM, Peter Rosin wrote:
> On 2016-09-23 19:39, Rob Herring wrote:
>> On Sat, Sep 17, 2016 at 11:34:22AM +0200, Peter Rosin wrote:
>>> From: Gustaf Lindström
>>>
>>> The Sharp 15" LQ150X1LG11 panel is an XGA TFT LCD panel.
>>>
>>> Signed-off-by: Gustaf Lindström
>>>
Adds the core gpu, and dsi nodes for the apq8064 needed
to get graphics working on the nexus7 and other devices.
These apply on top of Archit's patch set that enables HDMI for IFC6410
Feedback would be greatly appreciated!
Cc: Archit Taneja
Cc: vinay simha
Cc: andy.gross at linaro.org
Cc: robd
Add DSI and panel nodes to get graphics up and running
on the Nexus7.
This still depends on the panel driver being present
along with the rpmclk code.
Feedback would be greatly appreciated!
Cc: Archit Taneja
Cc: vinay simha
Cc: andy.gross at linaro.org
Cc: robdclark at gmail.com
Cc: linux-arm-
Add pstore support for the nexus7. This was useful in debugging
a crash where the cpus were getting stuck with irqs off and
serial output wasn't reliably working.
Cc: Kees Cook
Cc: Bjorn Andersson
Cc: Rob Clark
Cc: Stephen Boyd
Cc: Andy Gross
Cc: Vinay Simha
Cc: Archit Taneja
Cc: linux-arm-
On 09/23/2016 05:13 PM, John Stultz wrote:
> arch/arm/boot/dts/qcom-apq8064-asus-nexus7-flo.dts | 14 ++
> 1 file changed, 14 insertions(+)
>
> diff --git a/arch/arm/boot/dts/qcom-apq8064-asus-nexus7-flo.dts
> b/arch/arm/boot/dts/qcom-apq8064-asus-nexus7-flo.dts
> index 7637092..30055
On Fri, Sep 23, 2016 at 03:13:15PM +0200, Daniel Vetter wrote:
> Hm, maybe we should simply not call ->lastclose for kms drivers. That is
> kinda only a hack for ums/dri1 drivers.
Are you sure about that - isn't it needed so that the fbdev mode gets
restored when the last DRM user exits, so that t
On 2016-09-23 19:39, Rob Herring wrote:
> On Sat, Sep 17, 2016 at 11:34:22AM +0200, Peter Rosin wrote:
>> From: Gustaf Lindström
>>
>> The Sharp 15" LQ150X1LG11 panel is an XGA TFT LCD panel.
>>
>> Signed-off-by: Gustaf Lindström
>> Signed-off-by: Peter Rosin
>> ---
>> .../bindings/display/pa
When 'component_bind_all' fails it should not try to unbind components
in the error handling. This will produce a null pointer kernel panic when
no component exist.
This patch changes the order of the error handling. Now, it will only
unbind components if the are bound. Otherwise, the module will
On Fri, Sep 23, 2016 at 5:01 AM, Jyri Sarha wrote:
> On 09/23/16 14:47, Sean Paul wrote:
>> On Fri, Sep 23, 2016 at 3:52 AM, Daniel Schultz
>> wrote:
>>> When 'component_bind_all' fails it should not try to unbind components
>>> in the error handling. This will produce a null pointer kernel pani
Hi Maxime,
On 23 September 2016 at 23:16, Maxime Ripard
wrote:
> On Thu, Sep 22, 2016 at 08:03:31AM +1000, Jonathan Liu wrote:
>> Hi Maxime,
>>
>> On Thursday, 22 September 2016, Maxime Ripard > free-electrons.
>> com> wrote:
>>
>> > On Wed, Sep 21, 2016 at 11:03:04PM +1000, Jonathan Liu wrote:
>
On Fri, Sep 23, 2016 at 3:52 AM, Daniel Schultz wrote:
> When 'component_bind_all' fails it should not try to unbind components
> in the error handling. This will produce a null pointer kernel panic when
> no component exist.
>
> This patch changes the order of the error handling. Now, it will onl
Hi Tomi,
I added the missing check for "OMAP_DISPLAY_TYPE_VENC" in function
omap_connector_detect @ gpu/drm/omapdrm/omap_connector.c and now
modetest seems to be showing correct status and connections.
But still I could not see kmscube on panel and can see some flicker is
going on display. I thi
If 'ioremap()' returns 0, 'gm20b_tegra_read_wpr()' will return 0 as well,
which means success.
Return -ENOMEM instead
Signed-off-by: Christophe JAILLET
---
Not sure that -ENOMEM is the best value.
I've taken it because it is often used in such a case.
---
drivers/gpu/drm/nouveau/nvkm/subdev/secb
2016-09-22 Christian König :
> Am 22.09.2016 um 13:16 schrieb Gustavo Padovan:
> > 2016-09-22 Christian König :
> >
> > > Dropping the rest of the patch, cause that really doesn't make sense any
> > > more.
> > >
> > > Am 22.09.2016 um 12:40 schrieb Gustavo Padovan:
> > > > > E.g. for example
Dear Daniel,
Sorry for long response.
> Applied to drm-misc, thanks for the patch. Out of curiosity, how
> exactly did you spot this bug?
We use static analysis tools that check various rules on correct usage
of kernel core API. An example of error trace for the rm_dp_aux_dev case
you can see he
When I resume my desktop from suspend, the following shows up in the log.
Running 4.8.0-rc6 (net-next branch).dme
Everything appears to be working ok.
[148349.793696] PM: Syncing filesystems ... done.
[148350.599336] PM: Preparing system for sleep (mem)
[148350.599623] Freezing user space processe
101 - 131 of 131 matches
Mail list logo
