On Fri, Aug 04, 2017 at 08:20:32PM +1000, Daniel Axtens wrote:
> A system without PCI legacy resources (e.g. ARM64, powerpc) may
> find that no default/boot VGA device has been marked, because the
> VGA arbiter checks for legacy resource decoding before marking a
> card as default.
Would it be fea
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by work with
const attribute_group. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/gpu/drm/i915/i915_oa_hsw.c | 12 ++--
1 file changed, 6 insertio
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by work with
const attribute_group. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/gpu/drm/i915/i915_oa_sklgt3.c | 36 +--
Hi Lionel,
On Friday 04 August 2017 02:33 PM, Lionel Landwerlin wrote:
Hi Arwind,
These files were generated by a script maintained in this repository :
https://github.com/rib/gputop/blob/master/scripts/i915-perf-kernelgen.py
It would best to update this script first to make sure future
plat
The redundant fb helpers .load_lut, .gamma_set and .gamma_get are
no longer used. Remove the dead code that was not doing anything
sensible anyway.
Signed-off-by: Peter Rosin
---
drivers/staging/vboxvideo/vbox_fb.c | 15 ---
drivers/staging/vboxvideo/vbox_mode.c | 5 -
2 files
The redundant fb helpers .load_lut, .gamma_set and .gamma_get are
no longer used. Remove the dead code that was not doing anything
sensible anyway.
Signed-off-by: Peter Rosin
---
drivers/staging/vboxvideo/vbox_fb.c | 15 ---
drivers/staging/vboxvideo/vbox_mode.c | 5 -
2 files
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by work with
const attribute_group. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/gpu/drm/i915/i915_oa_bxt.c | 30 +++---
1 file c
Commit b60c1be74741 (dt-bindings: display/panel: Add common rotation property)
added the rotation property description in a new file. We have a place for
common display panel properties already. Move there the rotation property.
Acked-by: Noralf Trønnes
Acked-by: Rob Herring
Signed-off-by: Baruc
On Friday 04 August 2017 04:04 PM, Lionel Landwerlin wrote:
On 04/08/17 11:22, Arvind Yadav wrote:
Hi Lionel,
On Friday 04 August 2017 02:33 PM, Lionel Landwerlin wrote:
Hi Arwind,
These files were generated by a script maintained in this repository
:
https://github.com/rib/gputop/blob/m
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by work with
const attribute_group. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/gpu/drm/i915/i915_sysfs.c | 6 +++---
1 file changed, 3 insertions(+), 3
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by work with
const attribute_group. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/gpu/drm/i915/i915_oa_glk.c | 30 +++---
1 file c
On Fri, Aug 4, 2017 at 8:32 AM, Marek Szyprowski
wrote:
>
> Hi Krzysztof,
>
>
> On 2017-08-03 21:20, Krzysztof Kozlowski wrote:
>>
>> On Thu, Aug 03, 2017 at 09:45:23AM +0200, Maciej Purski wrote:
>>>
>>> This patch adds HDMI and Sil9234 MHL converter to Trats2 board.
>>
>> Just "Add HDMI...", wit
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by work with
const attribute_group. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/gpu/drm/i915/i915_oa_bdw.c | 44 +++---
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by work with
const attribute_group. So mark the non-const structs as const.
Arvind Yadav (11):
[PATCH 01/11] drm: i915: i915_oa_kblgt2: constify attribute_group structures.
[PATCH 02/11]
The Xilinx Video Mixer andn Xilinx Video Framebuffer DMA IP
support video memory formats that are not represented in the
current DRM fourcc library. This patch adds those missing
fourcc codes.
Signed-off-by: Jeffrey Mouroux
---
include/uapi/drm/drm_fourcc.h | 9 +
1 file changed, 9 inse
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by work with
const attribute_group. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/gpu/drm/i915/i915_oa_sklgt2.c | 36 +--
The following new fourcc codes introduced in patch 514b144b2dd7 (uapi: drm:
New fourcc codes needed by Xilinx Video IP) to DRM framework:
* AVUY
* VUY888
* XVUY
* XVUY2101010
* Y8
* Y10
* XV15
Signed-off-by: Jeffrey Mouroux
---
drivers/gpu/drm/drm_fourcc.c | 7 +++
1 file changed, 7 inse
This patch set is introduced to support a driver we are developing
for our new Video Framebuffer DMA IP, a DMA device that is "video format aware".
Clients need only specify memory layout information for a single plane
(i.e. luma) and then provide a video format code (e.g. YUV420) which will permit
Code added by commit 060e2ad57041b42c ("drm/vmwgfx: Add and connect plane helper
functions") is hitting KASAN error shown below. I guess that either *vcs is
invalid or vcs->is_implicit is off-by-one.
--
[ 19.654429] Linux agpgart interface v0.103
[ 19.657444] agpgart-intel :00:00.0
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by work with
const attribute_group. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/gpu/drm/i915/i915_oa_kblgt3.c | 36 +--
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by work with
const attribute_group. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/gpu/drm/i915/i915_oa_chv.c | 28 ++--
1 file cha
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by work with
const attribute_group. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/gpu/drm/i915/i915_oa_kblgt2.c | 36 +--
于 2017年8月4日 GMT+08:00 下午12:15:27, Chen-Yu Tsai 写到:
>Hi,
>
>On Tue, Aug 1, 2017 at 9:13 PM, Icenowy Zheng wrote:
>> From: Jernej Skrabec
>>
>> When setting the HDMI clock of H3, the PLL_VIDEO clock needs to be
>set.
>>
>> Add CLK_SET_RATE_PARENT flag for H3 HDMI clock.
>>
>> Signed-off-by: Jern
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by work with
const attribute_group. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/gpu/drm/i915/i915_oa_sklgt4.c | 36 +--
Fixes: 14da3ed8dd08 ("devicetree/bindings: display: Document common panel
properties")
Cc: Laurent Pinchart
Acked-by: Rob Herring
Signed-off-by: Baruch Siach
---
Documentation/devicetree/bindings/display/panel/panel-common.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a
Currently the hikey dsi logic cannot generate accurate byte
clocks values for all pixel clock values. Thus if a mode clock
is selected that cannot match the calculated byte clock, the
device will boot with a blank screen.
This patch uses the new mode_valid callback (many thanks to
Jose Abreu for u
I'm working on a VK_KHR_external_fence implementation based on this and
have found some issues. :-)
On Mon, Jul 17, 2017 at 11:44 PM, Dave Airlie wrote:
> From: Dave Airlie
>
> This interface will allow sync object to be used to back
> Vulkan fences. This API is pretty much the vulkan fence wai
On Saturday 05 Aug 2017 01:43:44 Laurent Pinchart wrote:
> Hello,
>
> This patch series is a third version of the code previously posted as
> "[PATCH v2 00/29] Remove the omapdrm and omapdss devices from platform
> code".
>
> The omapdss/omapdrm initialization code is quite a mess. The physical
>
The header file only contains four macros, two of which are never used.
Move the other two to dss.h and remove dss_features.h.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/dss/core.c | 1 -
drivers/gpu/drm/omapdrm/dss/dispc.c| 1 -
drivers/gpu/drm/omapdrm/dss/dpi
The supported outputs feature is specific to the DSS, move it from the
omap_dss_features structure to the dss driver.
The omap_dss_features structure is now empty and can be removed.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/dss/Makefile | 2 +-
drivers/gpu/drm/omapdrm
The FEAT_DPI_USES_VDDS_DSI feature is specific to the DPI, move it from
the omap_dss_features structure to the dpi code.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/dss/dpi.c | 13 -
drivers/gpu/drm/omapdrm/dss/dss_features.c | 2 --
drivers/gpu/drm/omapdrm/
The FEAT_HDMI_* features are specific to the HDMI4, move them from the
omap_dss_features structure to the hdmi4 driver.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/dss/dss_features.c | 5
drivers/gpu/drm/omapdrm/dss/dss_features.h | 2 --
drivers/gpu/drm/omapdrm/dss/hdmi.h
The FEAT_PARAM_DSS_PCD, FEAT_PARAM_LINEWIDTH and FEAT_PARAM_DOWNSCALE
features are specific to the DISPC, move them from the omap_dss_features
structure to the dispc driver.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/dss/dispc.c| 53 ++
driver
The FEAT_PARAM_DSS_FCK feature is specific to the DSS, move it from the
omap_dss_features structure to the dss driver.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/dss/dispc.c| 2 +-
drivers/gpu/drm/omapdrm/dss/dpi.c | 2 +-
drivers/gpu/drm/omapdrm/dss/dss.c
The FEAT_LCD_CLK_SRC feature is specific to the DSS, move it from the
omap_dss_features structure to the dss_features structure.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/dss/dss.c | 15 +++
drivers/gpu/drm/omapdrm/dss/dss_features.c | 4
drivers/gpu/
All the remaining FEAT_* features are specific to the DISPC, move them
from the omap_dss_features structure to the dispc driver.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/dss/dispc.c| 257 +
drivers/gpu/drm/omapdrm/dss/dss_features.c | 171 --
The FEAT_PARAM_DSI* features are specific to the DSI, move them from the
omap_dss_features structure to the dsi driver.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/dss/dsi.c | 25 +++--
drivers/gpu/drm/omapdrm/dss/dss_features.c | 6 --
drivers/g
The FEAT_VENC_REQUIRES_TV_DAC_CLK is specific to the VENC, move it from
the omap_dss_features structure to the venc driver.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/dss/dss_features.c | 2 --
drivers/gpu/drm/omapdrm/dss/dss_features.h | 1 -
drivers/gpu/drm/omapdrm/dss/venc.
The reg_fields feature describes DISPC registers only. Move it from the
omap_dss_features structure to the dispc_features structure.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/dss/dispc.c| 87 +
drivers/gpu/drm/omapdrm/dss/dss_features.c | 89
The overlay_caps is a dispc feature. Move it from the omap_dss_features
structure to the dispc_features structure.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/dss/dispc.c| 106 +++--
drivers/gpu/drm/omapdrm/dss/dss_features.c | 79
The FEAT_DSI_* features are specific to the DSI, move them from the
omap_dss_features structure to the dsi driver.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/dss/dsi.c | 137 ++---
drivers/gpu/drm/omapdrm/dss/dss_features.c | 16
drivers/gp
The register belongs to the DSS, move the feature to the dss_features
structure.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/dss/dss.c | 15 +++
drivers/gpu/drm/omapdrm/dss/dss.h | 5 +
drivers/gpu/drm/omapdrm/dss/dss_features.c | 10 --
The supported_color_modes is a dispc feature. Move it from the
omap_dss_features structure to the dispc_features structure.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/dss/dispc.c| 127 +++-
drivers/gpu/drm/omapdrm/dss/dss_features.c | 130
In preparation for removal of the core module, move the shutdown()
handler from core to dss.
Signed-off-by: Laurent Pinchart
Reviewed-by: Tomi Valkeinen
---
drivers/gpu/drm/omapdrm/dss/core.c | 20
drivers/gpu/drm/omapdrm/dss/dss.c | 16
2 files changed, 1
The DSS internal features are derived from the platform device
compatible string which is available at probe time. Don't delay
initialization until bind time. This prepares for the merge of the two
DSS features structures that will be needed before the DSS is bound.
Signed-off-by: Laurent Pinchart
The dss driver uses the supported display types to check whether the DSS
has SDI, VENC or HDMI outputs. We can instead use the supported outputs
the provide the same information. This removes the last use of the
supported display types, that we can then remove as well.
Signed-off-by: Laurent Pinch
The buffer_size_unit and burst_size_unit are dispc features. Move them
from the omap_dss_features structure to the dispc_features structure.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/dss/dispc.c| 25 +---
drivers/gpu/drm/omapdrm/dss/dss_features.c |
The num_ovls and num_mgrs are dispc features. Move them from the
omap_dss_features structure to the dispc_features structure.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/dss/dispc.c| 91 ++
drivers/gpu/drm/omapdrm/dss/dss_features.c | 30 --
Use the compatible string instead of the OMAP SoC revision to determine
device features. The various OMAP3-based SoCs can't be told apart using
the compatible string, use soc_device_match() to tell them apart.
Signed-off-by: Laurent Pinchart
Reviewed-by: Tomi Valkeinen
---
Changes since v2:
- F
debugfs code is spread between the core and dss drivers. In preparation
for removal of the core driver, move it all to the dss driver.
Signed-off-by: Laurent Pinchart
---
Changes since v2:
- Call dss_uninitialize_debugfs() in probe error path
- Remove empty #if defined() .. #endif leftover
---
The DSI PLL hardware data and DSS channels are selected based on the
OMAP SoC model. There's no need for fine-grained model information, as
the driver only needs to differentiate between OMAP3, OMAP4 and OMAP5.
As this can be done through the DSI compatible string, store the
corresponding informati
The OMAP implementation of the set_min_bus_tput() API is a no-op.
There's no point in forwarding the driver calls to the platform code.
Remove the use of the related platform data callback, but keep the
internal function as a reminder that the feature will need to be
implemented when the OMAP platf
Use the compatible string instead of the OMAP SoC revision to determine
device features. On OMAP34xx the features depend on the ES revision that
can not be determined from the compatible string. Use soc_device_match()
in that case.
Signed-off-by: Laurent Pinchart
Reviewed-by: Tomi Valkeinen
---
The DPI code only needs to differentiate between major OMAP revisions,
which can be obtained from the DSS compatible string. Replace the OMAP
SoC model checks to prepare for removal of the OMAP SoC version platform
data.
Signed-off-by: Laurent Pinchart
---
Changes since v2:
- Rename dss_device_t
Don't rely on callback functions provided by the platform, but access
the syscon internally to mux the DSI pins.
Signed-off-by: Laurent Pinchart
Reviewed-by: Tomi Valkeinen
---
drivers/gpu/drm/omapdrm/dss/core.c | 20 --
drivers/gpu/drm/omapdrm/dss/dsi.c | 82 ++
The dpi_display_enable() function ensures that a VDDS_DSI regulator is
available if the DSI uses the VDDS_DSI supply. This is not needed, as a
failure to get the VDDS_DSI supply will result in a probe failure,
dpi_display_enable() will thus never be called in that case.
Remove the check, and repla
Move the two function pointers to a new dss_ops structure. This will
allow merging the dss_features and omap_dss_features structures without
having to expose the DPI source selection and LCD clock muxing functions
in header files.
Signed-off-by: Laurent Pinchart
---
Changes since v2:
- Correctly
The two variables are never used outside of their compilation unit, make
them static.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/dss/omapdss.h | 7 ---
drivers/gpu/drm/omapdrm/dss/venc.c| 6 ++
2 files changed, 2 insertions(+), 11 deletions(-)
diff --git a/drivers/g
As non-DT booting is no longer supported, the only way to instantiate
the device is through an OF node, which is guaranteed to be present.
Remove the unneeded check.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/displays/panel-dpi.c | 3 +++
1 file changed, 3 insertions(+)
diff --
PHY features are stored in a global variable, while they should be
properties of the PHY object. As existing OMAP platforms have a single
HDMI PHY this doesn't cause any issue, but doesn't follow the driver
model.
Move the PHY features to the HDMI PHY data structure to follow the
driver model and
As non-DT booting is no longer supported, the only way to instantiate
the device is through an OF node, which is guaranteed to be present.
Remove the unneeded check.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/displays/connector-analog-tv.c | 3 +++
1 file changed, 3 insertions(+
As non-DT booting is no longer supported, the only way to instantiate
the device is through an OF node, which is guaranteed to be present.
Remove the unneeded check.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/displays/panel-sony-acx565akm.c | 3 +++
1 file changed, 3 insertions(
Hello,
This patch series is a third version of the code previously posted as
"[PATCH v2 00/29] Remove the omapdrm and omapdss devices from platform code".
The omapdss/omapdrm initialization code is quite a mess. The physical devices
are instantiated from DT, but two virtual devices named omapdrm
SoC device attributes are registered with a call to
soc_device_register() from the machine .init_late() operation, which is
called from the late initcall, after all drivers built-in drivers have
been probed. This results in the impossibility for drivers to use SoC
device matching in their probe fun
On Fri, Aug 4, 2017 at 4:43 PM, Eric Anholt wrote:
> Laurent Pinchart writes:
>
>> Hi Eric,
>>
>> (CC'ing Daniel)
>>
>> Thank you for the patch.
>>
>> On Tuesday 18 Jul 2017 14:05:06 Eric Anholt wrote:
>>> This will let drivers reduce the error cleanup they need, in
>>> particular the "is_panel_b
Hi David,
Thank you for the patch.
On Friday 04 Aug 2017 11:25:24 David Lechner wrote:
> The fbdev subsystem has a place for physical dimensions (width and height
> in mm) that is readable by userspace. Since DRM also knows these
> dimensions, pass this information to the fbdev device.
I'm curio
Hi Eric,
On Friday 04 Aug 2017 13:43:25 Eric Anholt wrote:
> Laurent Pinchart writes:
> > On Tuesday 18 Jul 2017 14:05:06 Eric Anholt wrote:
> >> This will let drivers reduce the error cleanup they need, in
> >> particular the "is_panel_bridge" flag.
> >>
> >> v2: Slight cleanup of remove functi
Boris Brezillon writes:
> On Tue, 18 Jul 2017 14:05:05 -0700
> Eric Anholt wrote:
>
>> The incoming mode might have a missing vrefresh field if it came from
>> drmModeSetCrtc(), which the kernel is supposed to calculate using
>> drm_mode_vrefresh(). We could either use that or the adjusted_mode
Daniel Stone writes:
> The IN_FORMATS blob allows the kernel to advertise to userspace which
> format/modifier combinations are supported, per plane. Use this to
> advertise that we support both T_TILED and linear.
>
> Signed-off-by: Daniel Stone
> ---
> drivers/gpu/drm/vc4/vc4_plane.c | 22 +++
Laurent Pinchart writes:
> Hi Eric,
>
> (CC'ing Daniel)
>
> Thank you for the patch.
>
> On Tuesday 18 Jul 2017 14:05:06 Eric Anholt wrote:
>> This will let drivers reduce the error cleanup they need, in
>> particular the "is_panel_bridge" flag.
>>
>> v2: Slight cleanup of remove function by And
https://bugs.freedesktop.org/show_bug.cgi?id=101377
--- Comment #11 from j...@dev1ce.com ---
initrd was rebuilt. Im purchasing another R9 380 card for further testing
(different manufacturer.) Its possible the build quality of the card is just
mediocre as ive seen numerous reports of problems re
Hi David,
On Friday 04 Aug 2017 10:51:37 David Lechner wrote:
> On 08/04/2017 09:54 AM, Laurent Pinchart wrote:
> > On Thursday 03 Aug 2017 17:33:47 David Lechner wrote:
> >> This adds a new binding for Sitronix ST7586 display panels.
> >>
> >> Using lego as the vendor prefix in the compatible st
Den 04.08.2017 18.51, skrev David Lechner:
On 08/04/2017 04:48 AM, Noralf Trønnes wrote:
Den 04.08.2017 00.33, skrev David Lechner:
This adds a new binding for Sitronix ST7586 display panels.
Using lego as the vendor prefix in the compatible string because the
display
panel I am working wi
Hi Laurent,
Den 04.08.2017 16.54, skrev Laurent Pinchart:
Hi David,
Thank you for the patch.
On Thursday 03 Aug 2017 17:33:47 David Lechner wrote:
This adds a new binding for Sitronix ST7586 display panels.
Using lego as the vendor prefix in the compatible string because the display
panel I
On 08/04/2017 04:48 AM, Noralf Trønnes wrote:
Den 04.08.2017 00.33, skrev David Lechner:
This adds a new binding for Sitronix ST7586 display panels.
Using lego as the vendor prefix in the compatible string because the
display
panel I am working with is an integral part of the LEGO MINDSTORMS
On 08/04/2017 11:22 AM, David Lechner wrote:
The fbdev subsystem has a place for physical dimensions (width and height
in mm) that is readable by userspace. Since DRM also knows these
dimensions, pass this information to the fbdev device.
This has to be done in drm_setup_crtcs_fb() instead of dr
The fbdev subsystem has a place for physical dimensions (width and height
in mm) that is readable by userspace. Since DRM also knows these
dimensions, pass this information to the fbdev device.
This has to be done in drm_setup_crtcs_fb() instead of drm_setup_crtcs()
because fb_helper->fbdev may be
The fbdev subsystem has a place for physical dimensions (width and height
in mm) that is readable by userspace. Since DRM also knows these
dimensions, pass this information to the fbdev device.
This has to be done in drm_setup_crtcs_fb() instead of drm_setup_crtcs()
because fb_helper->fbdev may be
On 04/08/17 11:39, Arvind Yadav wrote:
On Friday 04 August 2017 04:04 PM, Lionel Landwerlin wrote:
On 04/08/17 11:22, Arvind Yadav wrote:
Hi Lionel,
On Friday 04 August 2017 02:33 PM, Lionel Landwerlin wrote:
Hi Arwind,
These files were generated by a script maintained in this
repositor
On 08/04/2017 09:54 AM, Laurent Pinchart wrote:
Hi David,
Thank you for the patch.
On Thursday 03 Aug 2017 17:33:47 David Lechner wrote:
This adds a new binding for Sitronix ST7586 display panels.
Using lego as the vendor prefix in the compatible string because the display
panel I am working
Although etnaviv_drmif.h declared etna_bo_from_handle from the start,
there was no implementation.
Signed-off-by: Philipp Zabel
---
etnaviv/etnaviv_bo.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/etnaviv/etnaviv_bo.c b/etnaviv/etnaviv_bo.c
index 4fe877f1..75669572 1
Look up BOs from the name table using the name parameter instead of
req.handle (which at this point is always zero).
Signed-off-by: Philipp Zabel
Reviewed-by: Eric Engestrom
---
Sorry for the resend, this time to the correct list.
---
etnaviv/etnaviv_bo.c | 2 +-
1 file changed, 1 insertion(+),
Now CC'ing Daniel with his correct address :-/ I'll blame auto-completion in
my e-mail client. Sorry for the noise.
On Friday 04 Aug 2017 16:46:24 Laurent Pinchart wrote:
> Hi Eric,
>
> (CC'ing Daniel)
>
> Thank you for the patch.
>
> On Tuesday 18 Jul 2017 14:05:06 Eric Anholt wrote:
> > This
Hi David,
Thank you for the patch.
On Thursday 03 Aug 2017 17:33:47 David Lechner wrote:
> This adds a new binding for Sitronix ST7586 display panels.
>
> Using lego as the vendor prefix in the compatible string because the display
> panel I am working with is an integral part of the LEGO MINDST
Hi Tomi,
On Monday 15 May 2017 09:32:01 Tomi Valkeinen wrote:
> On 13/05/17 14:12, Laurent Pinchart wrote:
> >> Is it? You already use the dss compat string and soc_device_match to
> >> figure out some versions. Isn't that a proper way to find out about the
> >> SoC? But I agree that a more fine g
https://bugzilla.kernel.org/show_bug.cgi?id=196337
--- Comment #3 from Johannes Hirte (johannes.hi...@datenkhaos.de) ---
Created attachment 257811
--> https://bugzilla.kernel.org/attachment.cgi?id=257811&action=edit
Xorg.0.log
--
You are receiving this mail because:
You are watching the assign
https://bugzilla.kernel.org/show_bug.cgi?id=196337
--- Comment #2 from Johannes Hirte (johannes.hi...@datenkhaos.de) ---
Created attachment 257809
--> https://bugzilla.kernel.org/attachment.cgi?id=257809&action=edit
dmesg
--
You are receiving this mail because:
You are watching the assignee of
https://bugzilla.kernel.org/show_bug.cgi?id=196337
--- Comment #1 from Johannes Hirte (johannes.hi...@datenkhaos.de) ---
Still an issue with linux-4.13-rc3. I can login via ssh, so I can provide the
logs. Showing blocked tasks gives me this:
[ 620.046142] sysrq: SysRq : Show Blocked State
[ 620
https://bugs.freedesktop.org/show_bug.cgi?id=102008
bartos.p...@gmail.com changed:
What|Removed |Added
Component|Drivers/Gallium/radeonsi|Drivers/DRI/i965
QA Cont
Hi Eric,
(CC'ing Daniel)
Thank you for the patch.
On Tuesday 18 Jul 2017 14:05:06 Eric Anholt wrote:
> This will let drivers reduce the error cleanup they need, in
> particular the "is_panel_bridge" flag.
>
> v2: Slight cleanup of remove function by Andrzej
I just want to point out that, in th
On 07/31/2017 08:56 PM, Hans Verkuil wrote:
On 07/31/2017 04:29 PM, Russell King wrote:
The video setup path aways sets the clock disable register to a specific
value, which has the effect of disabling the CEC engine. When we add the
CEC driver, this becomes a problem.
Fix this by only setti
On 07/31/2017 08:55 PM, Hans Verkuil wrote:
On 07/31/2017 04:29 PM, Russell King wrote:
Add CEC notifier support to the HDMI bridge driver, so that the CEC
part of the IP can receive its physical address.
Signed-off-by: Russell King
Acked-by: Hans Verkuil
Queued to drm-misc-next.
Than
Den 04.08.2017 09.27, skrev Noralf Trønnes:
Den 04.08.2017 00.33, skrev David Lechner:
This adds parameters for vaddr and clip to
tinydrm_xrgb_to_gray8() to
make it more generic.
dma_buf_{begin,end}_cpu_access() are moved out to the repaper driver.
Signed-off-by: David Lechner
---
dr
Den 04.08.2017 00.33, skrev David Lechner:
This removes the call to mipi_dbi_init() from mipi_dbi_spi_init() so that
drivers can have a driver-specific implementation if needed.
Suggested-by: Noralf Trønnes
Signed-off-by: David Lechner
Reviewed-by: Noralf Trønnes
---
Thanks, applied to drm
Den 29.07.2017 19.24, skrev Stefan Agner:
On 2017-07-23 12:16, Noralf Trønnes wrote:
This driver can use the drm_driver.dumb_destroy and
drm_driver.dumb_map_offset defaults, so no need to set them.
Cc: Stefan Agner
Cc: Alison Wang
Signed-off-by: Noralf Trønnes
Acked-by: Stefan Agner
Tha
2017-07-25 14:33 GMT+02:00 Wladimir J. van der Laan :
> A relocation pointing to the last four bytes of a buffer can
> legitimately happen in the case of small vertex buffers.
>
> Signed-off-by: Wladimir J. van der Laan
Reviewed-by: Christian Gmeiner
> ---
> drivers/gpu/drm/etnaviv/etnaviv_gem
https://bugs.freedesktop.org/show_bug.cgi?id=101672
--- Comment #21 from MirceaKitsune ---
Created attachment 133244
--> https://bugs.freedesktop.org/attachment.cgi?id=133244&action=edit
Memtest86 screenshot
To rule out the possibility of a hardware issue, I ran two Memtest86 5.01
sessions fro
https://bugs.freedesktop.org/show_bug.cgi?id=100306
--- Comment #35 from MirceaKitsune ---
Created attachment 133243
--> https://bugs.freedesktop.org/attachment.cgi?id=133243&action=edit
Memtest86 screenshot
To rule out the possibility of a hardware issue, I ran two Memtest86 5.01
sessions fro
On 08/03/2017 05:20 PM, Arnd Bergmann wrote:
When CONFIG_PM is disabled, we get harmless warnings about unused
functions:
drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.c:1025:12: error: 'mdp5_runtime_resume'
defined but not used [-Werror=unused-function]
static int mdp5_runtime_resume(struct device
tree: git://people.freedesktop.org/~airlied/linux.git drm-syncobj-wait-null
head: 77645c44e3fc32028b3bef3b75889c1524b8df3a
commit: 77645c44e3fc32028b3bef3b75889c1524b8df3a [31/31] drm/syncobj: allow
wait on unsignalled semantics
reproduce: make htmldocs
All warnings (new ones prefixed by >>):
1 - 100 of 126 matches
Mail list logo
