Hi Linus,
Either my email ate everything or everyone is on holidays, either way
all I can find is some lonely AMD fixes.
Dave.
The following changes since commit 16f73eb02d7e1765ccab3d2018e0bd98eb93d973:
Linux 4.13-rc3 (2017-07-30 12:40:36 -0700)
are available in the git repository at:
The videomode structures are only copied into the vm field of a
panel_drv_data structure, so they can be const.
Done with the help of Coccinelle.
Signed-off-by: Julia Lawall
---
drivers/gpu/drm/omapdrm/displays/panel-lgphilips-lb035q02.c |2 +-
https://bugs.freedesktop.org/show_bug.cgi?id=101881
--- Comment #11 from Mike Lothian ---
So I think I've tracked this down
LLVM GCC 6.3.0 & Mesa GCC 6.3.0 Works
LLVM GCC 6.3.0 & Mesa GCC 7.1.0 Broken
LLVM GCC 7.1.0 & Mesa GCC 6.3.0 Works
LLVM GCC 7.1.0 & Mesa GCC 7.1.0
On Thu, 03 Aug 2017, Cihangir Akturk wrote:
> Indeed I used a simple shell script, which I included in the cover
> letter. But the cover letter doesn't seem to show up in the mailing
> list archives for some reason. I think I have done something wrong.
For intel-gfx it was in
https://bugs.freedesktop.org/show_bug.cgi?id=101881
--- Comment #12 from Mike Lothian ---
Hmm and I'm now seeing this in my dmesg when trying to launch Borderlands 2
[26293.375658] si_shader:1[28310]: segfault at 5 ip f2964d87 sp
f0cc3700 error 4 in
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #23 from Philipp Überbacher ---
(In reply to Shmerl from comment #22)
> Did anyone try to reproduce this bug with AMD kernel that supports display
> code (i.e. one with Vega support)?
The latest kernel I tried
Den 04.08.2017 00.41, skrev David Lechner:
On 08/01/2017 03:14 PM, David Lechner wrote:
If we return here and import_attach is true, then
dma_buf_end_cpu_access()
will not be called balance dma_buf_begin_cpu_access().
Fix by setting ret instead of returning.
Signed-off-by: David Lechner
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
---
https://bugs.freedesktop.org/show_bug.cgi?id=101881
--- Comment #14 from Mike Lothian ---
Borderlands 2 launches fine with both LLVM & Mesa are compiled with GCC 6.3.0
--
You are receiving this mail because:
You are the assignee for the
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...", without this patch.
Except few minor nitpicks below, looks good. After fixing I
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #24 from Shmerl ---
(In reply to Philipp Überbacher from comment #23)
>
> The latest kernel I tried this with is 4.12.3, does that qualify? (mesa
> 17.1.5, xf86-video-amdgpu 1.3.0).
Did you build it from here:
Hi Laurent,
Thanks for your detailed comments. Maciej resurrected some orphaned code,
which is still useful today (Tomasz has left Samsung a few years ago).
I'm not sure we will be able to answer all your questions without deep
investigation, especially about the driver operation details, but we
https://bugs.freedesktop.org/show_bug.cgi?id=101881
--- Comment #13 from Michel Dänzer ---
(In reply to Mike Lothian from comment #12)
> I'll try and figure out if that's LLVM or amd-staging-drm-next
It's the kernel, a separate issue from the one this report is about.
--
Hi,
> Here you go, compile tested version. :)
> 8<
> I want/need to rework the core property handling, and this hack is
> getting in the way. But since it's a non-standard propety only used by
> legacy userspace we know that this will only every be called from
> ioctl code. And never on
On Fri, Aug 4, 2017 at 11:57 AM, Tomi Valkeinen wrote:
>> Here you go, compile tested version. :)
>> 8<
>> I want/need to rework the core property handling, and this hack is
>> getting in the way. But since it's a non-standard propety only used by
>> legacy
On Wed, 2 Aug 2017 13:32:40 -0700
Eric Anholt wrote:
> It's also destroyed from the top level vc4_drv.c initialization, which
> is where the cache was actually initialized from.
>
> This used to just involve duplicate del_timer() and cancel_work_sync()
> being called, but it
On Wed, 2 Aug 2017 13:32:41 -0700
Eric Anholt wrote:
> The clocks are enabled/disabled at encoder enable/disable time, not at
> component load. Fixes a WARN_ON at boot if V3D fails to probe.
>
> Fixes: 4078f5757144 ("drm/vc4: Add DSI driver")
> Signed-off-by: Eric Anholt
On Wed, 2 Aug 2017 13:32:42 -0700
Eric Anholt wrote:
> drm_bridge_remove() is for unregistering a bridge driver, not for
s/driver/device/
> detaching a bridge from its consumer.
>
> Fixes: 656fa22f9cea ("drm/vc4: Switch DSI to the panel-bridge layer, and
> support
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
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/master/scripts/i915-perf-kernelgen.py
It would best to update
On Tue, 25 Jul 2017 09:27:33 -0700
Eric Anholt wrote:
> This is useful to allow GL to provide defined results for overlapping
> glBlitFramebuffer, which X11 in turn uses to accelerate uncomposited
> window movement without first blitting to a temporary. x11perf
> -copywinwin100
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
After an event is sent, we try to copy it into the user buffer of the
first waiter in drm_read() and if the user buffer doesn't have enough
room we put it back onto the list. However, we didn't wake up any
subsequent waiter, so that event may sit on the list until either a new
vblank event is sent
On Thu, Aug 03, 2017 at 11:19:09AM -0500, 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
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 platforms
get the fixes too.
Some changes have just been merged, deleted
On Tue, 18 Jul 2017 14:05:07 -0700
Eric Anholt wrote:
> The vc4 driver was unusual in that it was delaying the panel lookup
> until the attach step, while most DSI hosts will -EPROBE_DEFER until
> they get a panel.
>
> v2: Drop a debug message that slipped in.
>
>
On 3 August 2017 at 18:21, Ben Widawsky wrote:
> On 17-08-03 12:00:56, Daniel Stone wrote:
>> if (pipe >= PIPE_C || plane >= PLANE_SPRITE1)
>>
>> cf. skl_check_ccs_aux_surface() which rejects CCS on anything other
>> than PRIMARY/SPRITE0.
>>
>> I'll squash when pushing.
>
>
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 EV3.
Is this display available outside of
On Fri, Aug 4, 2017 at 6:12 AM, Michel Dänzer wrote:
> On 03/08/17 10:54 PM, Daniel Vetter wrote:
>> On Thu, Aug 3, 2017 at 1:17 AM, Daniel Vetter wrote:
>>> On Wed, Aug 2, 2017 at 10:50 PM, Alex Deucher wrote:
On Wed, Aug
omap_framebuffer_create() fails to unref all the gem objects if creating
the FB fails, leading to a memory leak.
Fix the loop so that it goes through all the reffed gem objects.
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/omapdrm/omap_fb.c | 2 +-
1 file changed, 1
On Tue, 25 Jul 2017 09:27:32 -0700
Eric Anholt wrote:
> Userspace shouldn't be able to spam dmesg by passing bad arguments.
> This has particularly become an issues since we started using a bad
> argument to set_tiling to detect if set_tiling was supported.
>
> Signed-off-by:
On Fri, Aug 04, 2017 at 12:49:29AM +0200, Peter Rosin wrote:
> On 2017-07-14 15:54, Daniel Vetter wrote:
> > On Thu, Jul 13, 2017 at 06:25:27PM +0200, Peter Rosin wrote:
> >> The legacy path implements setcmap in terms of crtc .gamma_set.
> >>
> >> The atomic path implements setcmap by directly
Hi Baruch,
Thank you for the patch.
On Friday 04 Aug 2017 08:38:45 Baruch Siach wrote:
> Fixes: 14da3ed8dd08 ("devicetree/bindings: display: Document common panel
> properties") Cc: Laurent Pinchart
>
> Acked-by: Rob Herring
>
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's
> original
Hi all,
Sorry to enter the discussion so late in the review process.
Eric, I'm replying here because this is where the initial discussion
happened, but I actually reviewed v5 of your patchset.
On Tue, 18 Jul 2017 13:13:04 -0700
Eric Anholt wrote:
> Archit Taneja
On 04/08/17 09:09, Julia Lawall wrote:
> The videomode structures are only copied into the vm field of a
> panel_drv_data structure, so they can be const.
>
> Done with the help of Coccinelle.
>
> Signed-off-by: Julia Lawall
>
> ---
>
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
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.
> >>
> >>
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
>
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
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
>>
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
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
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
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:
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.
>>
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
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
:
Fixes: 14da3ed8dd08 ("devicetree/bindings: display: Document common panel
properties")
Cc: Laurent Pinchart
Acked-by: Rob Herring
Signed-off-by: Baruch Siach
---
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
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
于 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
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
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 +++
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 |
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 |
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
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 +
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
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
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
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
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
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
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
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
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
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
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
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 |
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
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
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
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
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 ++--
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
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
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
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 +---
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 ++
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
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
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
---
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
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
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
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 --
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
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
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 +++
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 +
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 +++--
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 -
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 --
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 +++--
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 +
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 ++---
1 - 100 of 133 matches
Mail list logo