Remove obsolete drm_connector_register() call from tda998x_bind(). All
connectors are registered when drm_dev_register() is called by the
master drm_device driver.
Signed-off-by: Jyri Sarha
---
drivers/gpu/drm/i2c/tda998x_drv.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/drivers/gpu
A patch[1] that crashed all drm drivers using load() hook was briefly
part of linux-next, so became awave that tilcdc should stop using
that too.
The two first patches should be merged before the third can be
merged. So the merge order should be agreed with tda998x before going
forward.
The last
Stop using struct drm_driver load() callback. The load() callback
should not be used anymore. Instead the drm_device is allocated with
drm_dev_alloc() and registered with drm_dev_register() only after the
driver is completely initialized.
Signed-off-by: Jyri Sarha
---
drivers/gpu/drm/tilcdc/tilc
Use unload to handle initialization failures instead of complex goto
label mess. To do this the initialization sequence needed slight
reordering and some unload functions needed to become conditional.
Signed-off-by: Jyri Sarha
---
drivers/gpu/drm/tilcdc/tilcdc_drv.c | 91
Remove obsolete drm_connector_register() calls from tilcdc_panel.c and
tilcdc_tfp410.c. All connectors are registered when drm_dev_register()
is called.
Signed-off-by: Jyri Sarha
---
drivers/gpu/drm/tilcdc/tilcdc_panel.c | 2 --
drivers/gpu/drm/tilcdc/tilcdc_tfp410.c | 2 --
2 files changed, 4
Hi,
The text below describes how open source AMDGPU buffer sharing works.
I hope you'll find some useful bits in it.
Producer = allocates a buffer (or texture), and exports its handle
(DMABUF, etc.), and can use the buffer in various ways
Consumer = imports the handle, and can use the buffer in
Hi all,
After merging the drm-intel tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
drivers/gpu/drm/i915/gvt/execlist.c: In function 'release_shadow_batch_buffer':
drivers/gpu/drm/i915/gvt/execlist.c:501:4: warning:
'drm_gem_object_unreference' is deprecated [-Wdepr
Hi Laurent, John,
> > Here's what I'm using to get it working:
> > https://git.linaro.org/people/john.stultz/android-dev.git/commitdiff/1024cb4
> > 85b6f00a7e355ce60425f04a584481148
>
> Thank you.
>
> We need to standardize DT bindings for HDMI sound output. Morimoto-san, could
> you have a lo
-- next part ------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161019/8a7c3207/attachment.sig>
Hi Laurent,
Thanks for trying it out.
On 10/18/2016 6:37 PM, Laurent Pinchart wrote:
> Hi Jitendra,
>
> Thank you for the patch.
>
> On Tuesday 18 Oct 2016 15:39:58 Jitendra Sharma wrote:
>> Remove unused id_table entries
>> Currently this driver supports only device tree based configuration.
>>
On Wed, Oct 19, 2016 at 1:40 AM, Marek Olšák wrote:
> - The producer-consumer interop API doesn't know about the metadata.
> All you need to pass around is a buffer handle. (KMS, DMABUF, etc.)
> * There was a note during the talk that DMABUF doesn't have any
> metadata. Well, I just told you t
On Wed, Oct 19, 2016 at 2:08 AM, James Jones wrote:
>> * We can build upon this idea. I think the worst thing to do would
>> be to add metadata handling to driver-agnostic userspace APIs. Really,
>> driver-agnostic APIs shouldn't know about that, because they can't
>> understand all the hw-speci
On 18 October 2016 at 23:53, Dan Williams wrote:
> On Mon, Oct 17, 2016 at 8:48 PM, Dave Airlie wrote:
> [..]
Aren't there only 2 possibilities for this regression?
1/ a memtype entry was never made so track_pfn_insert() returns an
uncached mapping
2/ a conflicting m
On 19/10/16 08:40 AM, Marek Olšák wrote:
>
> 1) DRI (producer: application; consumer: X server)
> - The producer receives these flags: READ, EXPLICIT_FLUSH. The X
> server will treat the shared "texture" as read-only.
FWIW, no, the X server doesn't treat buffers shared with clients via DRI
as r
On Wed, Oct 19, 2016 at 12:07 AM, Philipp Zabel
wrote:
> Odd x/y offsets are not allowed for chroma subsampled planar YUV
> formats.
>
> Signed-off-by: Philipp Zabel
> ---
> drivers/gpu/drm/imx/ipuv3-plane.c | 8
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/gpu/drm/imx/ip
On Tue, 18 Oct 2016, Daniel Vetter wrote:
> On Tue, Oct 18, 2016 at 3:52 PM, Jani Nikula
> wrote:
>> On Tue, 18 Oct 2016, Daniel Vetter wrote:
>>> Needs new url-mapping information in nightly.conf to work properly.
>>
>> I think in the long run the right fix would be to make nightly.conf
>> inde
On Wed, Oct 19, 2016 at 12:07 AM, Philipp Zabel
wrote:
> Without this patch, after enabling the overlay plane with an RGBA
> framebuffer, switching to a framebuffer without alpha channel would
> cause the plane to vanish, since the pixel local alpha is constant
> zero in that case. Disable local
On Wed, Oct 19, 2016 at 12:07 AM, Philipp Zabel
wrote:
> If the framebuffer pixel format is planar YUV and unchanged, but the U
> or V plane offsets change, do not return an error, but request a modeset
> instead.
>
> Signed-off-by: Philipp Zabel
Acked-by: Liu Ying
> ---
> drivers/gpu/drm/im
On Wed, Oct 19, 2016 at 12:07 AM, Philipp Zabel
wrote:
> ipu_plane_atomic_set_base is called from ipu_plane_atomic_update in two
> different places, depending on whether drm_atomic_crtc_needs_modeset is
> true. Also depending on the same condition, this function does two
> different things.
> Thi
https://bugzilla.kernel.org/show_bug.cgi?id=178281
--- Comment #5 from fin4478 at hotmail.com ---
I did not have KVM support enabled in the kernel when using Kaveri. Enabling it
seems to stabilize amd-stagin-4.7 kernel so that sudden reboots do not happen,
I hope. TR 2013 I could tune so that the
On Tue, Oct 18, 2016 at 04:56:02PM +0100, Chris Wilson wrote:
> On Tue, Oct 18, 2016 at 05:16:23PM +0200, Arnd Bergmann wrote:
> > The introduction of reference counting on the state structures caused
> > sanitize_watermarks() in i915 to break in the error handling case,
> > as pointed out by gcc -
On Tue, Oct 18, 2016 at 01:57:19PM -0700, Stephen Boyd wrote:
> These GPU drivers only depend on the RESET_CONTROLLER config
> option to fix build issues that existed when there weren't stub
> reset APIs for reset controller consumers. Given that these
> drivers aren't providing any reset controlle
On Wed, Oct 19, 2016 at 12:33:55AM +0300, Jyri Sarha wrote:
> Stop using struct drm_driver load() callback. The load() callback
> should not be used anymore. Instead the drm_device is allocated with
> drm_dev_alloc() and registered with drm_dev_register() only after the
> driver is completely initi
On Wed, Oct 19, 2016 at 12:07 AM, Philipp Zabel
wrote:
> To support 4:2:2 or 4:4:4 chroma subsampling, divide the x/y offsets in
> drm_plane_state_to_ubo/vbo only if necessary for the given pixel format.
>
> Signed-off-by: Philipp Zabel
> ---
> drivers/gpu/drm/imx/ipuv3-plane.c | 27 +++
On Tue, Oct 18, 2016 at 10:42:46AM -0700, Stefan Agner wrote:
> On 2016-10-18 00:44, Daniel Vetter wrote:
> > On Mon, Oct 17, 2016 at 02:33:21PM -0700, Stefan Agner wrote:
> >> There is no need to request a CMA backed framebuffer if fbdev
> >> emulation is not enabled.
> >>
> >> Signed-off-by: Stef
On Wed, Oct 19, 2016 at 12:07 AM, Philipp Zabel
wrote:
> ipu_cpmem_set_fmt is already prepared to handle DRM_FORMAT_YVU422.
>
> Signed-off-by: Philipp Zabel
> ---
> drivers/gpu/ipu-v3/ipu-cpmem.c | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/gpu/ipu-v3/ipu-cpmem.c b/driv
On Wed, Oct 19, 2016 at 12:07 AM, Philipp Zabel
wrote:
> The IDMAC does support reading and writing DRM_FORMAT_YUV444 and
> DRM_FORMAT_YVU444.
>
> Signed-off-by: Philipp Zabel
> ---
> drivers/gpu/ipu-v3/ipu-common.c | 2 ++
> drivers/gpu/ipu-v3/ipu-cpmem.c | 17 +
> 2 files ch
On Wed, Oct 19, 2016 at 12:07 AM, Philipp Zabel
wrote:
> Hook up support for DRM_FORMAT_YUV422, DRM_FORMAT_YVU422,
> DRM_FORMAT_YUV444, DRM_FORMAT_YVU444, DRM_FORMAT_NV12,
> and DRM_FORMAT_NV16.
>
> Signed-off-by: Philipp Zabel
> ---
> drivers/gpu/drm/imx/ipuv3-plane.c | 52
> +
On Wed, Oct 19, 2016 at 12:07 AM, Philipp Zabel
wrote:
> If we want to stop resetting the IPU in the future, masking all
> interrupts before registering the irq handlers will not be enough to
> avoid spurious interrupts. We also have to clear them.
>
> Signed-off-by: Philipp Zabel
Acked-by: Liu
Hi Jyri,
Thank you for the patch.
On Wednesday 19 Oct 2016 00:33:56 Jyri Sarha wrote:
> Use unload to handle initialization failures instead of complex goto
> label mess. To do this the initialization sequence needed slight
> reordering and some unload functions needed to become conditional.
Whi
Hi Jyri,
Thank you for the patch.
On Wednesday 19 Oct 2016 00:33:54 Jyri Sarha wrote:
> Remove obsolete drm_connector_register() call from tda998x_bind(). All
> connectors are registered when drm_dev_register() is called by the
> master drm_device driver.
>
> Signed-off-by: Jyri Sarha
Acked-by
Hi Jyri,
Thank you for the patch.
On Wednesday 19 Oct 2016 00:33:53 Jyri Sarha wrote:
> Remove obsolete drm_connector_register() calls from tilcdc_panel.c and
> tilcdc_tfp410.c. All connectors are registered when drm_dev_register()
> is called.
>
> Signed-off-by: Jyri Sarha
Reviewed-by: Lauren
ARC PGU driver starts crashing on initialization after
'commit e12c2f645557 ("drm/i2c: adv7511: Convert to drm_bridge")'
This happenes because in "arcpgu_drm_hdmi_init" function we get pointer
of "drm_i2c_encoder_driver" structure, which doesn't exist after
adv7511 hdmi encoder interface changed fr
On Tue, Oct 18, 2016 at 06:07:49PM +0200, Philipp Zabel wrote:
> Odd x/y offsets are not allowed for chroma subsampled planar YUV
> formats.
>
> Signed-off-by: Philipp Zabel
> ---
> drivers/gpu/drm/imx/ipuv3-plane.c | 8
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/gpu/dr
2016-10-18 22:49 GMT+02:00 Laurent Pinchart :
> Hi Bartosz,
>
> Thank you for the patch.
>
> On Monday 17 Oct 2016 18:30:49 Bartosz Golaszewski wrote:
>> Create the driver for the da8xx System Configuration and implement
>> support for writing to the three Master Priority registers.
>>
>> Signed-of
Hi Russell,
On Wednesday 19 Oct 2016 09:16:30 Russell King - ARM Linux wrote:
> On Wed, Oct 19, 2016 at 10:54:06AM +0300, Laurent Pinchart wrote:
> > On Wednesday 19 Oct 2016 00:33:54 Jyri Sarha wrote:
> >> Remove obsolete drm_connector_register() call from tda998x_bind(). All
> >> connectors are
Hi Bartosz,
On Wednesday 19 Oct 2016 10:26:57 Bartosz Golaszewski wrote:
> 2016-10-18 22:49 GMT+02:00 Laurent Pinchart:
> > On Monday 17 Oct 2016 18:30:49 Bartosz Golaszewski wrote:
> >> Create the driver for the da8xx System Configuration and implement
> >> support for writing to the three Master
On 10/19/2016 01:16 PM, Eugeniy Paltsev wrote:
> ARC PGU driver starts crashing on initialization after
> 'commit e12c2f645557 ("drm/i2c: adv7511: Convert to drm_bridge")'
> This happenes because in "arcpgu_drm_hdmi_init" function we get pointer
> of "drm_i2c_encoder_driver" structure, which does
Hi Russell,
On Wednesday 19 Oct 2016 10:11:22 Russell King - ARM Linux wrote:
> On Wed, Oct 19, 2016 at 11:52:15AM +0300, Laurent Pinchart wrote:
> > On Wednesday 19 Oct 2016 09:16:30 Russell King - ARM Linux wrote:
> >> On Wed, Oct 19, 2016 at 10:54:06AM +0300, Laurent Pinchart wrote:
> >>> On We
Am Mittwoch, den 19.10.2016, 15:12 +0800 schrieb Ying Liu:
> On Wed, Oct 19, 2016 at 12:07 AM, Philipp Zabel
> wrote:
> > Odd x/y offsets are not allowed for chroma subsampled planar YUV
> > formats.
> >
> > Signed-off-by: Philipp Zabel
> > ---
> > drivers/gpu/drm/imx/ipuv3-plane.c | 8
Am Mittwoch, den 19.10.2016, 15:47 +0800 schrieb Ying Liu:
> On Wed, Oct 19, 2016 at 12:07 AM, Philipp Zabel
> wrote:
> > The IDMAC does support reading and writing DRM_FORMAT_YUV444 and
> > DRM_FORMAT_YVU444.
> >
> > Signed-off-by: Philipp Zabel
> > ---
> > drivers/gpu/ipu-v3/ipu-common.c | 2
Am Mittwoch, den 19.10.2016, 10:58 +0300 schrieb Ville Syrjälä:
> On Tue, Oct 18, 2016 at 06:07:49PM +0200, Philipp Zabel wrote:
> > Odd x/y offsets are not allowed for chroma subsampled planar YUV
> > formats.
> >
> > Signed-off-by: Philipp Zabel
> > ---
> > drivers/gpu/drm/imx/ipuv3-plane.c
Am Mittwoch, den 19.10.2016, 15:49 +0800 schrieb Ying Liu:
[...]
> > @@ -406,10 +425,16 @@ static void ipu_plane_atomic_update(struct drm_plane
> > *plane,
> > switch (fb->pixel_format) {
> > case DRM_FORMAT_YUV420:
> > case DRM_FORMAT_YVU420:
> > + case DRM_FORMAT_YU
Op 10-08-16 om 16:14 schreef Daniel Vetter:
> On Wed, Aug 10, 2016 at 12:46:23PM +0200, Maarten Lankhorst wrote:
>> When doing a atomic commit affecting multiple crtc's, multiple events
>> are generated. The user_data member does not allow you to distinguish,
>> because they all have the same point
Hi Jyri,
I believe this will break mali-dp and hdlcd, unless something changed
while I wasn't looking. Please see this previous thread where I did
the same thing and then had to have it reverted: [1]
Before removing this, we need to refactor (at least) mali-dp and hdlcd
to move drm_dev_register()
On Wed 19-10-16 09:58:15, Lorenzo Stoakes wrote:
> On Tue, Oct 18, 2016 at 05:30:50PM +0200, Michal Hocko wrote:
> > I am wondering whether we can go further. E.g. it is not really clear to
> > me whether we need an explicit FOLL_REMOTE when we can in fact check
> > mm != current->mm and imply that
On Wed, Oct 19, 2016 at 11:52:15AM +0300, Laurent Pinchart wrote:
> Hi Russell,
>
> On Wednesday 19 Oct 2016 09:16:30 Russell King - ARM Linux wrote:
> > On Wed, Oct 19, 2016 at 10:54:06AM +0300, Laurent Pinchart wrote:
> > > On Wednesday 19 Oct 2016 00:33:54 Jyri Sarha wrote:
> > >> Remove obsole
On Tue, Oct 18, 2016 at 05:30:50PM +0200, Michal Hocko wrote:
> I am wondering whether we can go further. E.g. it is not really clear to
> me whether we need an explicit FOLL_REMOTE when we can in fact check
> mm != current->mm and imply that. Maybe there are some contexts which
> wouldn't work, I
On Wed 19-10-16 09:40:45, Lorenzo Stoakes wrote:
> On Wed, Oct 19, 2016 at 10:13:52AM +0200, Michal Hocko wrote:
> > On Wed 19-10-16 09:59:03, Jan Kara wrote:
> > > On Thu 13-10-16 01:20:18, Lorenzo Stoakes wrote:
> > > > This patch removes the write parameter from __access_remote_vm() and
> > > >
On Wed, Oct 19, 2016 at 10:13:52AM +0200, Michal Hocko wrote:
> On Wed 19-10-16 09:59:03, Jan Kara wrote:
> > On Thu 13-10-16 01:20:18, Lorenzo Stoakes wrote:
> > > This patch removes the write parameter from __access_remote_vm() and
> > > replaces it
> > > with a gup_flags parameter as use of thi
On Wed 19-10-16 09:59:03, Jan Kara wrote:
> On Thu 13-10-16 01:20:18, Lorenzo Stoakes wrote:
> > This patch removes the write parameter from __access_remote_vm() and
> > replaces it
> > with a gup_flags parameter as use of this function previously _implied_
> > FOLL_FORCE, whereas after this patch
On Thu 13-10-16 01:20:14, Lorenzo Stoakes wrote:
> This patch removes the write and force parameters from get_user_pages_locked()
> and replaces them with a gup_flags parameter to make the use of FOLL_FORCE
> explicit in callers as use of this flag can result in surprising behaviour
> (and
> hence
On Thu 13-10-16 01:20:15, Lorenzo Stoakes wrote:
> This patch removes the write and force parameters from get_vaddr_frames() and
> replaces them with a gup_flags parameter to make the use of FOLL_FORCE
> explicit
> in callers as use of this flag can result in surprising behaviour (and hence
> bugs
On Wed, Oct 19, 2016 at 10:54:06AM +0300, Laurent Pinchart wrote:
> Hi Jyri,
>
> Thank you for the patch.
>
> On Wednesday 19 Oct 2016 00:33:54 Jyri Sarha wrote:
> > Remove obsolete drm_connector_register() call from tda998x_bind(). All
> > connectors are registered when drm_dev_register() is cal
Hi Archit, all,
On Wed, 2016-10-19 at 14:43 +0530, Archit Taneja wrote:
>
> On 10/19/2016 01:16 PM, Eugeniy Paltsev wrote:
> >
> > ARC PGU driver starts crashing on initialization after
> > 'commit e12c2f645557 ("drm/i2c: adv7511: Convert to drm_bridge")'
> > This happenes because in "arcpgu_drm
On Thu 13-10-16 01:20:18, Lorenzo Stoakes wrote:
> This patch removes the write parameter from __access_remote_vm() and replaces
> it
> with a gup_flags parameter as use of this function previously _implied_
> FOLL_FORCE, whereas after this patch callers explicitly pass this flag.
>
> We make thi
On Thu 13-10-16 01:20:16, Lorenzo Stoakes wrote:
> This patch removes the write and force parameters from get_user_pages() and
> replaces them with a gup_flags parameter to make the use of FOLL_FORCE
> explicit
> in callers as use of this flag can result in surprising behaviour (and hence
> bugs)
On Tue 18-10-16 14:56:09, Lorenzo Stoakes wrote:
> On Tue, Oct 18, 2016 at 02:54:25PM +0200, Jan Kara wrote:
> > > @@ -1282,7 +1282,7 @@ long get_user_pages(unsigned long start, unsigned
> > > long nr_pages,
> > > int write, int force, struct page **pages,
> > >
On Thu 13-10-16 01:20:17, Lorenzo Stoakes wrote:
> This patch removes the write and force parameters from get_user_pages_remote()
> and replaces them with a gup_flags parameter to make the use of FOLL_FORCE
> explicit in callers as use of this flag can result in surprising behaviour
> (and
> hence
On Wed, Oct 19, 2016 at 12:19:30PM +0300, Laurent Pinchart wrote:
> Hi Russell,
>
> On Wednesday 19 Oct 2016 10:11:22 Russell King - ARM Linux wrote:
> > In any case, I don't agree with converting it to a DRM bridge - that will
> > mean that we have to split the driver into two pieces, the bridge
On Wed, Oct 19, 2016 at 10:52:05AM +0200, Michal Hocko wrote:
> yes this is the desirable and expected behavior.
>
> > wonder if this is desirable behaviour or whether this ought to be limited to
> > ptrace system calls. Regardless, by making the flag more visible it makes it
> > easier to see that
On Wed 19-10-16 10:06:46, Lorenzo Stoakes wrote:
> On Wed, Oct 19, 2016 at 10:52:05AM +0200, Michal Hocko wrote:
> > yes this is the desirable and expected behavior.
> >
> > > wonder if this is desirable behaviour or whether this ought to be limited
> > > to
> > > ptrace system calls. Regardless,
Free memory mapping, if hdmi_probe is not successful.
Signed-off-by: Arvind Yadav
---
drivers/gpu/drm/exynos/exynos_hdmi.c |5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/gpu/drm/exynos/exynos_hdmi.c
b/drivers/gpu/drm/exynos/exynos_hdmi.c
index 2275efe..ba28dec 100644
--- a/
To support 4:2:2 or 4:4:4 chroma subsampling, divide the x/y offsets in
drm_plane_state_to_ubo/vbo only if necessary for the given pixel format.
Signed-off-by: Philipp Zabel
---
drivers/gpu/drm/imx/ipuv3-plane.c | 27 ++-
1 file changed, 18 insertions(+), 9 deletions(-)
The IDMAC does support reading and writing DRM_FORMAT_YUV444 and
DRM_FORMAT_YVU444.
Signed-off-by: Philipp Zabel
Acked-by: Liu Ying
---
Changes since v1:
- Drop change to ipu_cpmem_set_yuv_planar, which has been removed
---
drivers/gpu/ipu-v3/ipu-common.c | 2 ++
drivers/gpu/ipu-v3/ipu-cpmem.c
Odd x/y offsets are not allowed for horizontally/vertically chroma
subsampled planar YUV formats.
Signed-off-by: Philipp Zabel
---
Changes since v1:
- Improve comment
---
drivers/gpu/drm/imx/ipuv3-plane.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/gpu/drm/imx/ipuv3
Hook up support for DRM_FORMAT_YUV422, DRM_FORMAT_YVU422,
DRM_FORMAT_YUV444, DRM_FORMAT_YVU444, DRM_FORMAT_NV12,
and DRM_FORMAT_NV16.
Signed-off-by: Philipp Zabel
---
Changes since v1:
- Make UBO/VBO swap for YVU formats more obvious in ipu_plane_atomic_update
---
drivers/gpu/drm/imx/ipuv3-plan
ipu_cpmem_set_yuv_planar_full is only used directly, remove the wrapper.
Suggested-by: Liu Ying
Signed-off-by: Philipp Zabel
---
drivers/gpu/ipu-v3/ipu-cpmem.c | 36
include/video/imx-ipu-v3.h | 2 --
2 files changed, 38 deletions(-)
diff --git a/drive
Without this patch, after enabling the overlay plane with an RGBA
framebuffer, switching to a framebuffer without alpha channel would
cause the plane to vanish, since the pixel local alpha is constant
zero in that case. Disable local alpha again when setting an opaque
framebuffer.
Signed-off-by: P
If the framebuffer pixel format is planar YUV and unchanged, but the U
or V plane offsets change, do not return an error, but request a modeset
instead.
Signed-off-by: Philipp Zabel
Acked-by: Liu Ying
---
drivers/gpu/drm/imx/ipuv3-plane.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions
If we want to stop resetting the IPU in the future, masking all
interrupts before registering the irq handlers will not be enough to
avoid spurious interrupts. We also have to clear them.
Signed-off-by: Philipp Zabel
Acked-by: Liu Ying
---
drivers/gpu/ipu-v3/ipu-common.c | 5 -
1 file chang
ipu_plane_atomic_set_base is called from ipu_plane_atomic_update in two
different places, depending on whether drm_atomic_crtc_needs_modeset is
true. Also depending on the same condition, this function does two
different things.
This patch removes the indirection by merging the relevant parts into
Use drm_plane_helper_check_state to clip raw user coordinates to crtc
bounds. This checks for full plane coverage and scaling already, so
we can drop some custom checks. Use the clipped coordinates everywhere.
Suggested-by: Ville Syrjälä
Signed-off-by: Philipp Zabel
---
drivers/gpu/drm/imx/ip
On Wed, Oct 19, 2016 at 12:21:17PM +0200, Philipp Zabel wrote:
> Use drm_plane_helper_check_state to clip raw user coordinates to crtc
> bounds. This checks for full plane coverage and scaling already, so
> we can drop some custom checks. Use the clipped coordinates everywhere.
>
> Suggested-by: V
On Wed, Oct 19, 2016 at 8:42 AM, Dave Airlie wrote:
> On 18 October 2016 at 23:53, Dan Williams wrote:
>> On Mon, Oct 17, 2016 at 8:48 PM, Dave Airlie wrote:
>> [..]
> Aren't there only 2 possibilities for this regression?
>
> 1/ a memtype entry was never made so track_pfn_insert() r
Am Mittwoch, den 19.10.2016, 13:31 +0300 schrieb Ville Syrjälä:
> On Wed, Oct 19, 2016 at 12:21:17PM +0200, Philipp Zabel wrote:
> > Use drm_plane_helper_check_state to clip raw user coordinates to crtc
> > bounds. This checks for full plane coverage and scaling already, so
> > we can drop some c
--
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161019/4fe1e31b/attachment.html>
on the bug is
not present.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161019/0a2562d9/attachment.html>
On Tue, 18 Oct 2016, Chris Wilson wrote:
> On Tue, Oct 18, 2016 at 02:28:35PM +0300, Jani Nikula wrote:
>> Fixes sparse warnings:
>>
>> drivers/gpu/drm/drm_debugfs_crc.c:118:30: warning: symbol
>> 'drm_crtc_crc_control_fops' was not declared. Should it be static?
>>
>> drivers/gpu/drm/drm_debugf
On Tue, 18 Oct 2016, "Sharma, Shashank" wrote:
> Reviewed-by: Shashank Sharma
Both pushed to drm-intel-next-queued, thanks for the review.
RB,
Jani.
>
> Regards
> Shashank
> -Original Message-
> From: Nikula, Jani
> Sent: Tuesday, October 18, 2016 4:52 PM
> To: intel-gfx at lists.freed
https://bugzilla.kernel.org/show_bug.cgi?id=178281
Nicolai Hähnle changed:
What|Removed |Added
CC||nhaehnle at gmail.com
--- Comment #6 f
Remove redundant condition check
Remove not necessary if-else block for checking DT entry because else
part will never be picked as in absence of device node, probe will
fail in initial stage only.
Remove unused id->driver_data entries
As id->driver_data is not used in driver source. So no need in
Fix warnings on building htmldocs.
Fixes: 056996b95686 ("drm: Helper for lspcon in drm_dp_dual_mode")
Cc: Rodrigo Vivi
Cc: Shashank Sharma
Cc:
Signed-off-by: Jani Nikula
---
n.b. 056996b95686 ("drm: Helper for lspcon in drm_dp_dual_mode") has
been merged via drm-intel tree
---
drivers/gpu/d
Hi Jitendra,
Thank you for the patch.
On Wednesday 19 Oct 2016 17:12:48 Jitendra Sharma wrote:
> Remove redundant condition check
> Remove not necessary if-else block for checking DT entry because else
> part will never be picked as in absence of device node, probe will
> fail in initial stage on
On Wed, Oct 19, 2016 at 02:43:24PM +0300, Jani Nikula wrote:
> Fix warnings on building htmldocs.
>
> Fixes: 056996b95686 ("drm: Helper for lspcon in drm_dp_dual_mode")
> Cc: Rodrigo Vivi
> Cc: Shashank Sharma
> Cc:
> Signed-off-by: Jani Nikula
>
> ---
>
> n.b. 056996b95686 ("drm: Helper for
Fix warnings on building htmldocs.
v2: whitespace around '/' (Ville)
Fixes: 056996b95686 ("drm: Helper for lspcon in drm_dp_dual_mode")
Cc: Rodrigo Vivi
Cc: Shashank Sharma
Cc:
Signed-off-by: Jani Nikula
---
n.b. 056996b95686 ("drm: Helper for lspcon in drm_dp_dual_mode") has
been merged vi
Am 19.10.2016 um 08:23 schrieb Daniel Vetter:
> On Wed, Oct 19, 2016 at 1:40 AM, Marek Olšák wrote:
>> - The producer-consumer interop API doesn't know about the metadata.
>> All you need to pass around is a buffer handle. (KMS, DMABUF, etc.)
>>* There was a note during the talk that DMABUF
= 228,
> + },
> + .bus_format = MEDIA_BUS_FMT_RGB565_1X16,
This doesn't match the .bpc = 8 above. You'd usually use a .bpc = 6 for
RGB565 panels.
Thierry
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161019/d7f6d758/attachment.sig>
ing towards just applying this with .bpc set to 6 and hope for
the best (and fix it if somebody finds that it's broken).
So no need to resend, just let me know what you think.
Thierry
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161019/59630dac/attachment.sig>
On 19.10.2016 01:40, Marek Olšák wrote:
> * We can build upon this idea. I think the worst thing to do would
> be to add metadata handling to driver-agnostic userspace APIs. Really,
> driver-agnostic APIs shouldn't know about that, because they can't
> understand all the hw-specific information
ture
Size: 801 bytes
Desc: not available
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161019/2255e529/attachment-0001.sig>
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161019/1f6d7174/attachment.sig>
Desc: not available
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161019/8e2680c2/attachment.sig>
https://bugzilla.kernel.org/show_bug.cgi?id=178281
--- Comment #7 from fin4478 at hotmail.com ---
There is just boot traces in dmesg, journalctl and Xorg.0.log when my computer
desktop hangs and checking with ssh.
--
You are receiving this mail because:
You are watching the assignee of the bug.
On Wed, Oct 19, 2016 at 7:39 AM, Thierry Reding
wrote:
> On Tue, Sep 06, 2016 at 04:46:16PM +0200, Maxime Ripard wrote:
>> Netron DY is a brand of LCD panels found on SBCs and tablets.
>>
>> Signed-off-by: Maxime Ripard
>> ---
>> Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
>> 1
Hi Laurent,
On 10/19/2016 5:21 PM, Laurent Pinchart wrote:
> Hi Jitendra,
>
> Thank you for the patch.
>
> On Wednesday 19 Oct 2016 17:12:48 Jitendra Sharma wrote:
>> Remove redundant condition check
>> Remove not necessary if-else block for checking DT entry because else
>> part will never be pi
erspace drivers only. The kernel driver isn't supposed to read it or
parse it. The format is negotiated between userspace driver developers for
sharing of more complex allocations than 2D displayable surfaces.
Marek
> -Daniel
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161019/f4e50c12/attachment-0001.html>
Hi.,
On 10/19/2016 6:37 PM, Sharma, Jitendra wrote:
> Hi Laurent,
>
>
> On 10/19/2016 5:21 PM, Laurent Pinchart wrote:
>> Hi Jitendra,
>>
>> Thank you for the patch.
>>
>> On Wednesday 19 Oct 2016 17:12:48 Jitendra Sharma wrote:
>>> Remove redundant condition check
>>> Remove not necessary if-else
2016-10-06 22:09 GMT+09:00 Tobias Jakobi :
> Hello,
>
> I think this patch was never picked up. So just a short 'ping' from my side.
>
Oops. one I missed. Will pick it up soon.
Thanks,
Inki Dae
> With best wishes,
> Tobias
>
>
> Shuah Khan wrote:
>> Fix exynos_drm_gem_create() error messages to
Hi Jitendra,
On Wednesday 19 Oct 2016 18:37:38 Sharma, Jitendra wrote:
> On 10/19/2016 5:21 PM, Laurent Pinchart wrote:
> > On Wednesday 19 Oct 2016 17:12:48 Jitendra Sharma wrote:
> >> Remove redundant condition check
> >> Remove not necessary if-else block for checking DT entry because else
> >>
1 - 100 of 174 matches
Mail list logo
