On Fri, Nov 4, 2016 at 9:23 PM, Eric Engestrom wrote:
> On Friday, 2016-11-04 13:50:25 -0400, Rob Clark wrote:
>> On Fri, Nov 4, 2016 at 1:32 PM, Eric Engestrom
>> wrote:
>> > On Friday, 2016-11-04 13:12:51 -0400, Rob Clark wrote:
>> >> On Fri, Nov 4, 2016 at 12:27 PM, Ville Syrjälä
>> >>
.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161104/e61fb438/attachment.html>
:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161104/e146f5c3/attachment.html>
--
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161104/d1b3957c/attachment.html>
6CAC A448 860C DC13
-- next part --
A non-text attachment was scrubbed...
Name: digikam-screenshot.jpg
Type: image/jpeg
Size: 271932 bytes
Desc: not available
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161104/3caf2533/attachment-0001.jpg>
...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161104/0a80319a/attachment-0001.html>
On Fri, Nov 04, 2016 at 01:50:25PM -0400, Rob Clark wrote:
> On Fri, Nov 4, 2016 at 1:32 PM, Eric Engestrom
> wrote:
> > On Friday, 2016-11-04 13:12:51 -0400, Rob Clark wrote:
> >> On Fri, Nov 4, 2016 at 12:27 PM, Ville Syrjälä
> >> wrote:
> >> > On Fri, Nov 04, 2016 at 11:32:45AM -0400, Rob
On Fri, Nov 04, 2016 at 11:32:45AM -0400, Rob Clark wrote:
> Fixes: 90844f00049e9f42573fd31d7c32e8fd31d3fd07
>
> drm: make drm_get_format_name thread-safe
>
> Signed-off-by: Eric Engestrom
> [danvet: Clarify that the returned pointer must be freed with
> kfree().]
>
On Fri, Nov 04, 2016 at 01:38:25PM -0700, Linus Torvalds wrote:
> On Wed, Nov 2, 2016 at 5:31 PM, Dave Airlie wrote:
> >
> > There are a set of fixes for an oops we've been seeing around MST
> > display unplug,
>
> Side note: I heard from a couple of people at the KS that said that
> they had
When the VSP1 is used in an active display pipeline, the output of the
WPF can supply the LIF entity directly and simultaneously write to
memory.
Support this functionality in the VSP1 driver, by extending the WPF
source pads, and establishing a V4L2 video device node connected to the
new source.
This reverts commit 3299ba5c0b21 ("[media] v4l: vsp1: Supply frames to
the DU continuously")
The DU output mode does not rely on frames being supplied on the WPF as
its pipeline is supplied from DRM. For the upcoming WPF writeback
functionality, we will choose to enable writeback mode if there is
Resending this patch series to bring in dri-devel, and interested parties.
Apologies for the resend to linux-media and linux-renesas-soc.
This short series extends the VSP1 on the RCar platforms to allow creating a
V4L2 video node on display pipelines where the hardware allows writing to
memory
On Sat, Nov 05, 2016 at 02:25:19AM +0900, Norbert Preining wrote:
> Hi Chris,
>
> > https://cgit.freedesktop.org/drm-intel/
>
> I pulled from there and rebuild my kernel. Rebooting and everything
> is fine. Looks much better!!!
>
> >
> -Original Message-
> From: Sumit Semwal [mailto:sumit.semwal at linaro.org]
> Sent: Friday, November 04, 2016 1:15 PM
> To: Alex Deucher
> Cc: amd-gfx at lists.freedesktop.org; DRI mailing list; Zhang, Jerry; Deucher,
> Alexander
> Subject: Re: [PATCH 2/3] drm/amdgpu: add the interface
Fixes: 90844f00049e9f42573fd31d7c32e8fd31d3fd07
drm: make drm_get_format_name thread-safe
Signed-off-by: Eric Engestrom
[danvet: Clarify that the returned pointer must be freed with
kfree().]
Signed-off-by: Daniel Vetter
Note (Rob Clark):
I think we need to be a bit
On Friday, 2016-11-04 13:12:51 -0400, Rob Clark wrote:
> On Fri, Nov 4, 2016 at 12:27 PM, Ville Syrjälä
> wrote:
> > On Fri, Nov 04, 2016 at 11:32:45AM -0400, Rob Clark wrote:
> >> Fixes: 90844f00049e9f42573fd31d7c32e8fd31d3fd07
> >>
> >> drm: make drm_get_format_name thread-safe
> >>
> >>
On Tue, Oct 25, 2016 at 6:23 AM, Matthias Brugger
wrote:
>
> On 10/18/2016 04:37 PM, Enric Balletbo Serra wrote:
> [...]
>>> --- /dev/null
>>> +++ b/drivers/gpu/drm/bridge/parade-ps8640.c
> [...]
>>>
>>> +
>>> +/* Firmware */
>>> +#define PS_FW_NAME "ps864x_fw.bin"
>>> +
>>
>> From
On Sat, Nov 05, 2016 at 03:55:03AM +1100, Stephen Rothwell wrote:
> Hi Liviu,
>
> On Fri, 4 Nov 2016 15:48:02 + Liviu Dudau wrote:
> >
> > Brian Starkey is a co-maintainer for the Mali DP tree, so his Signed-off-by
> > alone should be good. Baoyou's patch is in my tree to stop him repeatedly
Hi Liviu,
On Thu, 3 Nov 2016 17:19:58 + Liviu Dudau wrote:
>
> I have revamped the mali-dp tree and rebased it on the newer
> version of drm-next (which includes the drm-misc change) and pushed the
> updated patch in my tree.
Thanks for that. However, several of the commits in your tree
The pm_runtime_put() we were using immediately released power on the
device, which meant that we were generally turning the device off and
on once per frame. In many profiles I've looked at, that added up to
about 1% of CPU time, but this could get worse in the case of frequent
rendering and
From: Junwei Zhang
v2: agd: rebase and squash in all the previous optimizations and
changes so everything compiles.
v3: squash in Slava's 32bit build fix
v4: rebase on drm-next (fence -> dma_fence),
squash in Monk's ioctl update patch
Signed-off-by: Junwei Zhang
From: "monk.liu"
Return the index of the first signaled fence. This information
is useful in some APIs like Vulkan.
v2: rebase on drm-next (fence -> dma_fence)
Signed-off-by: monk.liu
Signed-off-by: Alex Deucher
Cc: Sumit Semwal
---
This is the same patch set I send out
Hi Alex,
Thanks for the patches.
On 4 November 2016 at 14:16, Alex Deucher wrote:
> From: "monk.liu"
>
> Return the index of the first signaled fence. This information
> is useful in some APIs like Vulkan.
>
> v2: rebase on drm-next (fence -> dma_fence)
>
> Signed-off-by: monk.liu
>
On Fri, Nov 04, 2016 at 04:38:54PM +1100, Stephen Rothwell wrote:
> Hi Liviu,
>
> On Thu, 3 Nov 2016 17:19:58 + Liviu Dudau wrote:
> >
> > I have revamped the mali-dp tree and rebased it on the newer
> > version of drm-next (which includes the drm-misc change) and pushed the
> > updated
assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161104/5b292b35/attachment.html>
https://bugzilla.kernel.org/show_bug.cgi?id=185681
--- Comment #7 from René Linder ---
https://cgit.freedesktop.org/~agd5f/linux/commit/drivers/gpu/drm/amd/powerplay?h=drm-fixes-4.9=025f8bfb84cbcaa78df31ab00d7e3c5f979e9e27
there is the iceland_get_evv_voltage who works ... and the new
to enable
> > it.
>
> Have you been working on this or should I have a look?
I have not been. Please have a look. Thanks!
--
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/20161104/98f1ee2d/attachment.html>
On Thu, 2016-10-27 at 19:14 -0700, Robert Bragg wrote:
> Being able to program OACONTROL from a non-privileged batch buffer is
> not sufficient to be able to configure the OA unit. This was originally
> allowed to help enable Mesa to expose OA counters via the
> INTEL_performance_query extension,
https://bugzilla.kernel.org/show_bug.cgi?id=185681
--- Comment #6 from René Linder ---
I found some missing / wrong parts, if i look at the handle of PP_TABLE_V0 and
PP_TABLE_V1 Handling there is through the whole code everytime a direct access
to V0 = hwmgr-> V1 = table_info->
And i never
On Thu, 2016-10-27 at 19:14 -0700, Robert Bragg wrote:
> Consistent with the kernel.perf_event_paranoid sysctl option that can
> allow non-root users to access system wide cpu metrics, this can
> optionally allow non-root users to access system wide OA counter metrics
> from Gen graphics hardware.
On Thu, 2016-10-27 at 19:14 -0700, Robert Bragg wrote:
> Each metric set is given a sysfs entry like:
>
> /sys/class/drm/card0/metrics//id
>
> This allows userspace to enumerate the specific sets that are available
> for the current system. The 'id' file contains an unsigned integer that
> can
On Thu, 2016-10-27 at 19:14 -0700, Robert Bragg wrote:
> Adds base i915 perf infrastructure for Gen performance metrics.
>
> This adds a DRM_IOCTL_I915_PERF_OPEN ioctl that takes an array of uint64
> properties to configure a stream of metrics and returns a new fd usable
> with standard VFS
The DP device identification string read from the DPCD registers is 6
characters long at max. and we store it in a char array of the same length
without space for the NULL terminator. Fix this by increasing the array
size to 7 and initialize it to an empty string.
Signed-off-by: Dhinakaran
he video yo YouTube.
Cheers
--
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/20161104/b1b9174a/attachment.html>
bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161104/2a04d54e/attachment.html>
the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161104/f71c9576/attachment.html>
On Fri, Nov 4, 2016 at 1:32 PM, Eric Engestrom
wrote:
> On Friday, 2016-11-04 13:12:51 -0400, Rob Clark wrote:
>> On Fri, Nov 4, 2016 at 12:27 PM, Ville Syrjälä
>> wrote:
>> > On Fri, Nov 04, 2016 at 11:32:45AM -0400, Rob Clark wrote:
>> >> Fixes: 90844f00049e9f42573fd31d7c32e8fd31d3fd07
>> >>
Bartosz Golaszewski writes:
> Create the driver for the da8xx master peripheral priority
> configuration and implement support for writing to the three
> Master Priority registers on da850 SoCs.
>
> Signed-off-by: Bartosz Golaszewski
Reviewed-by: Kevin Hilman
Bartosz Golaszewski writes:
> Create a new driver for the da8xx DDR2/mDDR controller and implement
> support for writing to the Peripheral Bus Burst Priority Register.
>
> Signed-off-by: Bartosz Golaszewski
Reviewed-by: Kevin Hilman
er.
--
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/20161104/8095454c/attachment.html>
On Wed, Nov 2, 2016 at 5:31 PM, Dave Airlie wrote:
>
> There are a set of fixes for an oops we've been seeing around MST
> display unplug,
Side note: I heard from a couple of people at the KS that said that
they had had problems with suspend/resume after plugging in to a 4k
display (but _only_ a
char __user *buf,
> > + size_t count,
> > + loff_t *ppos)
> > +{
> > + struct i915_perf_stream *stream = file->private_data;
> > + struct drm_i915_private *dev_priv = stream->dev_priv;
> > + ssize_t ret;
> > +
> > + if (!(file->f_flags & O_NONBLOCK)) {
> > + /* Allow false positives from stream->ops->wait_unlocked.
> > + */
> > + do {
> > + ret = stream->ops->wait_unlocked(stream);
> > + if (ret)
> > + return ret;
> > +
> > + mutex_lock(_priv->perf.lock);
>
> Should interruptible version be used here, to allow for reads to be
> interrupted?
>
Now that we don't have the context pin hook on haswell we could /almost/
get away without this lock except for its use to synchronize
i915_perf_register with i915_perf_open_ioctl.
Most of the i915-perf state access is synchronized as a result of being
fops driven, so this perf.lock was added to deal with a few entrypoints
outside of fops such as the contect pinning hook we used to have (though we
avoid it in the hrtimer callback).
Although the recent change to remove the pin hook has made the lock look a
bit redundant for now, I think I'd prefer to leave the locks as they are to
avoid the churn with the gen8+ patches where we do have some other
entrypoints into i915-perf outside of the fops.
Given that though, there's currently not really much argument either way
for them being interruptible. The expectation I have atm is that there
shouldn't be anything running async within i915-perf outside of fops that's
expected to be long running. We will probably also want to consider the
risk of bouncing lots of reads, starving userspace and increasing the risk
of a buffer overflow if this is interruptible.
- Robert
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161104/b52b433c/attachment-0001.html>
On Fri, Nov 4, 2016 at 12:27 PM, Ville Syrjälä
wrote:
> On Fri, Nov 04, 2016 at 11:32:45AM -0400, Rob Clark wrote:
>> Fixes: 90844f00049e9f42573fd31d7c32e8fd31d3fd07
>>
>> drm: make drm_get_format_name thread-safe
>>
>> Signed-off-by: Eric Engestrom
>> [danvet: Clarify that the
are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161104/21e815c9/attachment.html>
On Fri, Nov 04, 2016 at 08:40:47PM +0900, Norbert Preining wrote:
> Dear all,
>
> since 4.9-rc series started I see heavy redraw problems on i915. Starting
> or resizing for example the digikam window messes up completely the content.
>
> I have seen this at least since rc2 (I often wait till
.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161104/da157071/attachment.html>
On Fri, Nov 4, 2016 at 11:32 AM, Rob Clark wrote:
> Fixes: 90844f00049e9f42573fd31d7c32e8fd31d3fd07
>
> drm: make drm_get_format_name thread-safe
>
> Signed-off-by: Eric Engestrom
> [danvet: Clarify that the returned pointer must be freed with
> kfree().]
> Signed-off-by:
pedef, I guess I just followed that style.
> >
> Kernel coding style advises against both typedefs and CamelCase. We do
> have a few "offenders" but it's better to not add more.
>
> Ftw when in doubt do search/grep through the document - I don't thinks
> there's many people who've read the thing in one go :-)
Ah thanks, I'll get rid of the CamelCase!
Christophe
-- 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/20161104/8881115e/attachment.sig>
ertain setups?
This seems a bit overkill to me, but I can look into it if needed.
Christophe
-- 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/20161104/6199a45d/attachment.sig>
Hi Alex,
Thanks for this patch. Adding Gustavo as well.
On 3 November 2016 at 11:41, Alex Deucher wrote:
> From: "monk.liu"
>
> Return the index of the first signaled fence. This information
> is useful in some APIs like Vulkan.
>
> Signed-off-by: monk.liu
> Signed-off-by: Alex Deucher
>
On 4 November 2016 at 11:14, Sumit Semwal wrote:
> Hi Alex,
>
> Thanks for the patch!
>
> On 3 November 2016 at 11:41, Alex Deucher wrote:
>> From: Junwei Zhang
>>
>> v2: agd: rebase and squash in all the previous optimizations and
>> changes so everything compiles.
>> v3: squash in Slava's
Fixes: 90844f00049e9f42573fd31d7c32e8fd31d3fd07
drm: make drm_get_format_name thread-safe
Signed-off-by: Eric Engestrom
[danvet: Clarify that the returned pointer must be freed with
kfree().]
Signed-off-by: Daniel Vetter
Note: I think we need to be a bit careful about
Hi Alex,
Thanks for the patch!
On 3 November 2016 at 11:41, Alex Deucher wrote:
> From: Junwei Zhang
>
> v2: agd: rebase and squash in all the previous optimizations and
> changes so everything compiles.
> v3: squash in Slava's 32bit build fix
>
> Signed-off-by: Junwei Zhang
> Reviewed-by:
in dmesg before the "ring stalled" messages?
--
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/20161104/328d7aa2/attachment.html>
On Thu, 2016-10-27 at 19:14 -0700, Robert Bragg wrote:
> check_cmd() is checking whether a command adheres to certain
> restrictions that ensure it's safe to execute within a privileged batch
> buffer. Returning false implies a privilege problem, not that the
> command is invalid.
>
> The
The validation for it ends up being quite simple, but I hadn't got
around to it before merging the driver. For backwards compatibility,
we also need to add a flag so that the userspace GL driver can easily
tell if the kernel will allow ETC1 textures (on an old kernel, it will
continue to convert
The loop is scanning until the original max_ip (size of the BO), but
we want to not examine any code after the PROG_END's delay slots.
There was a block trying to do that, except that we had some early
continue statements if the signal wasn't a PROG_END or a BRANCH.
The failure mode would be that
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/20161104/4b753bde/attachment-0001.html>
On Fri, Nov 4, 2016 at 6:44 AM, Jan Beulich wrote:
On 13.09.16 at 17:54, wrote:
>> While a hard hang in atom_asic_init() likely points at a deeper problem
>> in the driver, restore the capability to boot a Xen Dom0 by simply
>> avoiding the call there: Other than for Xen DomU, Dom0 owning a
ves/dri-devel/attachments/20161104/b0347084/attachment.html>
.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161104/0ca97842/attachment.html>
>>> On 04.11.16 at 15:32, wrote:
> On Fri, Nov 4, 2016 at 6:44 AM, Jan Beulich wrote:
> On 13.09.16 at 17:54, wrote:
>>> While a hard hang in atom_asic_init() likely points at a deeper problem
>>> in the driver, restore the capability to boot a Xen Dom0 by simply
>>> avoiding the call
bedded Linux and Kernel engineering
http://free-electrons.com
-- 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/20
On 03.11.2016 13:53, ville.syrjala at linux.intel.com wrote:
> From: Ville Syrjälä
>
> All the VICs apart from 58 and 59 have the word "Hz" included in the
> comment. Include it for 59 and 59 as well.
>
> Cc: Shashank Sharma
> Cc: Andrzej Hajda
> Signed-off-by: Ville Syrjälä
Reviewed-by:
https://bugzilla.kernel.org/show_bug.cgi?id=185681
--- Comment #5 from René Linder ---
If i go back to where the Powermanagment (smu7_hwmgr.c) where the commit
change:
Since Commit: ab4f06d3adcc5165b13ed2e657050fd1808f319b (agd5f/linux
origin/drm-fixes-4.9
-
If 'sun4i_layers_init()' returns an error, propagate it instead of
returning -EINVAL unconditionally.
Signed-off-by: Christophe JAILLET
---
drivers/gpu/drm/sun4i/sun4i_drv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/sun4i/sun4i_drv.c
Hi Stefan,
>
> How did you actually test that? I have a hard time to get anything useable
> with
> this code.
>
> The display looks completely borked (colors are way off, and at random either
> too dark or too bright).
>
> I then also added Gamma 1.0 (and different values) to the Monitor
>>> On 13.09.16 at 17:54, wrote:
> While a hard hang in atom_asic_init() likely points at a deeper problem
> in the driver, restore the capability to boot a Xen Dom0 by simply
> avoiding the call there: Other than for Xen DomU, Dom0 owning a device
> does not really mean is has got passed through
ably be better to make this a Hz based threshold for
userspace, otherwise any userspace policy here needs to be adapted for each
system with a different timestamp frequency which isn't great.
I've updated the patch locally to make this an oa_max_sample_rate parameter
in Hz, which I'll aim to test on haswell tomorrow and send out.
Thanks,
- Robert
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161104/e60f1a57/attachment.html>
e you been working on this or should I have a look?
--
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/20161104/4ddf9b25/attachment-0001.html>
On Thu, Nov 03, 2016 at 07:34:02PM -0400, Rob Clark wrote:
> On Thu, Nov 3, 2016 at 5:41 PM, Chris Wilson
> wrote:
> > static bool dma_fence_array_enable_signaling(struct dma_fence *fence)
> > {
> > struct dma_fence_array *array = to_dma_fence_array(fence);
> > int num_pending =
71 matches
Mail list logo