On 23 May 2018 at 19:13, Russell King wrote:
> On Wed, May 23, 2018 at 10:48:15AM +0200, Daniel Vetter wrote:
>> On Tue, May 22, 2018 at 09:27:07AM +0100, Russell King wrote:
>> > On Tue, May 22, 2018 at 10:53:49AM +1000, Dave Airlie wrote:
>> > > Sorry I missed this, just
Hi Linus,
Only two sets of drivers fixes, one rcar-du lvds regression fix, and a
group of fixes for vmwgfx.
Regards,
Dave.
The following changes since commit 771c577c23bac90597c685971d7297ea00f99d11:
Linux 4.17-rc6 (2018-05-20 15:31:38 -0700)
are available in the Git repository at:
On 05/23/2018 02:46 PM, Juergen Gross wrote:
On 23/05/18 13:36, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
Building for a 32-bit target results in warnings from casting
between a 32-bit pointer and a 64-bit integer. Fix the warnings
by
Hi, Stu:
On Fri, 2018-05-25 at 10:34 +0800, stu.hs...@mediatek.com wrote:
> From: Stu Hsieh
>
> This patch create third crtc by third ddp path
>
Apply this patch before the patch 'Add support for mediatek SOC MT2712'
because this patch is necessary for mt2712.
>
Hi, Stu:
I've some inline comment.
On Fri, 2018-05-25 at 10:34 +0800, stu.hs...@mediatek.com wrote:
> From: Stu Hsieh
>
> This patch add support for the Mediatek MT2712 DISP subsystem.
> There are two OVL engine and three disp output in MT2712.
>
> Signed-off-by: Stu
When checking for a dependency fence for belonging to the same entity
compare it with scheduled as well finished fence. Earlier we were only
comparing it with the scheduled fence.
Signed-off-by: Nayan Deshmukh
---
drivers/gpu/drm/scheduler/gpu_scheduler.c | 9
Signed-off-by: Nayan Deshmukh
---
Documentation/gpu/drm-mm.rst | 18 ++
1 file changed, 18 insertions(+)
diff --git a/Documentation/gpu/drm-mm.rst b/Documentation/gpu/drm-mm.rst
index b08e9dcd9177..96ebcc2a7b41 100644
--- a/Documentation/gpu/drm-mm.rst
convert existing raw comments into kernel-doc format as well
as add new documentation
Signed-off-by: Alex Deucher
Signed-off-by: Nayan Deshmukh
---
drivers/gpu/drm/scheduler/gpu_scheduler.c | 214 --
Hi, Stu:
On Fri, 2018-05-25 at 10:34 +0800, stu.hs...@mediatek.com wrote:
> From: Stu Hsieh
>
> This patch add component AAL1 and
> rename AAL to AAL0
>
> Signed-off-by: Stu Hsieh
> ---
> drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.h | 3 ++-
> 1
Hi, Stu:
On Fri, 2018-05-25 at 10:34 +0800, stu.hs...@mediatek.com wrote:
> From: Stu Hsieh
>
> This patch add the connection from OD1 to RDMA1 for ext path.
>
Reviewed-by: CK Hu
> Signed-off-by: Stu Hsieh
> ---
>
Hi, Stu:
On Fri, 2018-05-25 at 10:34 +0800, stu.hs...@mediatek.com wrote:
> From: Stu Hsieh
>
> This patch support that if modules more than 32,
> add index more than 31 when using DISP_REG_MUTEX_MOD2 bit
>
Reviewed-by: CK Hu
> Signed-off-by: Stu
Hi, Stu:
On Fri, 2018-05-25 at 10:34 +0800, stu.hs...@mediatek.com wrote:
> From: Stu Hsieh
>
> Update device tree binding documentation for the display subsystem for
> Mediatek MT2712 SoCs.
>
I've acked v2 of this patch and v3 is the same as v2, so you should keep
my
Hi Heiko, Sandy,
On Fri, May 25, 2018 at 7:07 AM Heiko Stübner wrote:
> From: Sandy Huang
> The vop irq is shared between vop and iommu and irq probing in the
> iommu driver moved to the probe function recently. This can in some
> cases lead to a stall if
From: Stu Hsieh
This patch support that if modules more than 32,
add index more than 31 when using DISP_REG_MUTEX_MOD2 bit
Signed-off-by: Stu Hsieh
---
drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 75 +-
1 file
From: Stu Hsieh
This patch add component PWM2
Signed-off-by: Stu Hsieh
---
drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.h
From: Stu Hsieh
This patch create third crtc by third ddp path
Signed-off-by: Stu Hsieh
---
drivers/gpu/drm/mediatek/mtk_drm_drv.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/gpu/drm/mediatek/mtk_drm_drv.c
From: Stu Hsieh
This patch add the component OD1 and
rename the OD to OD1
Signed-off-by: Stu Hsieh
---
drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
From: Stu Hsieh
This patch add support for the Mediatek MT2712 DISP subsystem.
MT2712 is base on MT8173, there are some difference as following:
MT2712 support three disp output(two ovl and one rdma)
Change in v3:
- Added patch for ddp component AAL1
- Added patch for
From: Stu Hsieh
This patch add component AAL1 and
rename AAL to AAL0
Signed-off-by: Stu Hsieh
---
drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
From: Stu Hsieh
This patch add support for the Mediatek MT2712 DISP subsystem.
There are two OVL engine and three disp output in MT2712.
Signed-off-by: Stu Hsieh
---
drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 46 +++--
From: Stu Hsieh
This patch add the connection from OD1 to RDMA1 for ext path.
Signed-off-by: Stu Hsieh
---
drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/mediatek/mtk_drm_ddp.c
From: Stu Hsieh
Update device tree binding documentation for the display subsystem for
Mediatek MT2712 SoCs.
Signed-off-by: Stu Hsieh
---
Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt | 2 +-
1 file changed, 1
On Thu, May 24, 2018, 9:26 PM Haneen Mohammed
wrote:
> This patch add checks for atomic_[duplicate/destroy]_state of
> drm_[connector/crtc/plane]_funcs for atomic drivers in the relevant
> drm_*_init functions since these callback are mandatory for atomic drivers.
>
>
On 2018-03-20 04:01, Archit Taneja wrote:
Hi,
On Tuesday 20 March 2018 01:28 AM, Sean Paul wrote:
Instead of subclassing atomic state, store driver private data in
private_obj/state. This allows us to remove the swap_state driver hook
for mdp5 and get closer to using the atomic helpers
From: Sandy Huang
The vop irq is shared between vop and iommu and irq probing in the
iommu driver moved to the probe function recently. This can in some
cases lead to a stall if the irq is triggered while the vop driver
still has it disabled.
But there is no real need to
On Thu, May 24, 2018 at 1:50 AM, Maxime Ripard
wrote:
> On Mon, May 21, 2018 at 07:27:46PM +0200, Jernej Škrabec wrote:
>> Hi,
>>
>> Dne ponedeljek, 21. maj 2018 ob 10:07:59 CEST je Maxime Ripard napisal(a):
>> > On Sat, May 19, 2018 at 08:31:18PM +0200, Jernej Skrabec
https://bugs.freedesktop.org/show_bug.cgi?id=106441
--- Comment #5 from Richard B. Kreckel ---
It must be Xorg.
I've upgradee to Xorg 1.20 (without upgrading anything else) from
Debian/experimental and this problem has disappeared for good.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=106430
--- Comment #3 from mikhail.v.gavri...@gmail.com ---
A very strange coincidence:
Every time I reproduce the described bug case with GPU hangup while playing a
video with VAAPI acceleration.
The following messages will appear in the kernel log
https://bugs.freedesktop.org/show_bug.cgi?id=106631
--- Comment #10 from Jan Vesely ---
(In reply to Ricardo Ribalda from comment #9)
> (In reply to Ricardo Ribalda from comment #8)
> > I am using llvm/clang from https://github.com/kraj/meta-clang . Can you
> > point me
https://bugs.freedesktop.org/show_bug.cgi?id=106519
--- Comment #20 from mikhail.v.gavri...@gmail.com ---
(In reply to Alex Deucher from comment #18)
>
> H.264 works fine. Not sure what's happening with your system.
It turns out I was running the old version of mpv and not the new one which
https://bugs.freedesktop.org/show_bug.cgi?id=106597
Lukas Wunner changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugzilla.kernel.org/show_bug.cgi?id=199425
--- Comment #6 from mikita.lip...@amd.com (mikita.lip...@amd.com) ---
Created attachment 276173
--> https://bugzilla.kernel.org/attachment.cgi?id=276173=edit
Patch to either dublicate or reuse an existing crtc state that might pervent
https://bugs.freedesktop.org/show_bug.cgi?id=106517
--- Comment #4 from Dhinakaran Pandiyan ---
(In reply to arkadiusz.hi...@intel.com from comment #3)
> Hey,
>
> Is this request for an freedesktop account at the same time? Because you
> need one to get the commit
There is currently a mixture of octal and symbolic permissions uses
in files in drivers/gpu/drm and one file in drivers/gpu.
There are ~270 existing octal uses and ~115 S_ uses.
Convert all the S_ symbolic permissions to their octal equivalents
as using octal and not symbolic permissions is
From: Ville Syrjälä
Fix up a bunch of bad indentation and insconsistent comments
in edid_cea_modes[].
v2: Instead of stripping the aspect ratio comments let's
add them to all modes
Signed-off-by: Ville Syrjälä
---
Fixes: 9b4c412a654c ("drm/amdgpu: Add static CG control for VCN on RV")
Signed-off-by: kbuild test robot
---
vcn_v1_0.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/vcn_v1_0.c
tree: git://people.freedesktop.org/~agd5f/linux.git drm-next-4.18-wip
head: 27bd044dd054fed87166c831b6d38bc609e733cc
commit: 9b4c412a654ce71ad0e81044d3300677a7668ac8 [114/129] drm/amdgpu: Add
static CG control for VCN on RV
reproduce:
# apt-get install sparse
git checkout
https://bugzilla.kernel.org/show_bug.cgi?id=199425
--- Comment #5 from mikita.lip...@amd.com (mikita.lip...@amd.com) ---
Created attachment 276171
--> https://bugzilla.kernel.org/attachment.cgi?id=276171=edit
Patch to either dublicate or reuse an existing crtc state that might pervent
https://bugs.freedesktop.org/show_bug.cgi?id=106548
--- Comment #7 from Francesco Balestrieri ---
Created attachment 139741
--> https://bugs.freedesktop.org/attachment.cgi?id=139741=edit
DMESG output
Kernel logs
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=106631
--- Comment #9 from Ricardo Ribalda ---
(In reply to Ricardo Ribalda from comment #8)
> I am using llvm/clang from https://github.com/kraj/meta-clang . Can you
> point me to something to check if the debug mode is
https://bugs.freedesktop.org/show_bug.cgi?id=106631
--- Comment #8 from Ricardo Ribalda ---
I am using llvm/clang from https://github.com/kraj/meta-clang . Can you point
me to something to check if the debug mode is enabled or not?
Thanks
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=106631
--- Comment #7 from Jan Vesely ---
It looks like even 100s is not enough. Can you try running with no time limit?
(set to 0).
Looking at the numbers I think mesa's results are inflated by the kernel
getting killed before
https://bugs.freedesktop.org/show_bug.cgi?id=106597
--- Comment #33 from taij...@posteo.de ---
(In reply to Alex Deucher from comment #32)
> (In reply to taijian from comment #30)
> > Created attachment 139739 [details] [review] [review]
> > patch that seems to fix things for me
> >
> > OK,
On Wed, May 23, 2018 at 06:44:00PM -0700, Abhinav Kumar wrote:
> Add support for Truly NT35597 panel used
> in MSM reference platforms.
>
> This panel supports both single DSI and dual DSI
> modes.
>
> However, this patch series adds support only for
> dual DSI mode.
>
> Changes in v3:
> -
https://bugs.freedesktop.org/show_bug.cgi?id=106519
--- Comment #19 from mikhail.v.gavri...@gmail.com ---
(In reply to Alex Deucher from comment #18)
> H.264 works fine. Not sure what's happening with your system.
Which info needed?
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=106597
--- Comment #32 from Alex Deucher ---
(In reply to taijian from comment #30)
> Created attachment 139739 [details] [review]
> patch that seems to fix things for me
>
> OK, going with Lukas' discovery, I have rebuild my
https://bugs.freedesktop.org/show_bug.cgi?id=106519
--- Comment #18 from Alex Deucher ---
(In reply to mikhail.v.gavrilov from comment #17)
> (In reply to Alex Deucher from comment #16)
> > vega10 does not support VP9.
> Here
https://bugs.freedesktop.org/show_bug.cgi?id=106519
--- Comment #17 from mikhail.v.gavri...@gmail.com ---
(In reply to Alex Deucher from comment #16)
> vega10 does not support VP9.
Here https://www.phoronix.com/scan.php?page=news_item=AMD-VP9-VAAPI-VCN
I am here that AMD Posts VP9 VA-API Video
On Fri, 2018-05-18 at 13:00 -0400, Jan Vesely wrote:
> Fixes memory leak on module unload.
> Analogous to mesa commit of the same name.
> Signed-off-by: Jan Vesely
> ---
> amdgpu/amdgpu_device.c | 4
> 1 file changed, 4 insertions(+)
>
> diff --git
On 05/24/2018 12:14 PM, Daniel Vetter wrote:
On Thu, May 24, 2018 at 11:25:04AM +0200, Thomas Hellstrom wrote:
On 05/24/2018 10:32 AM, Daniel Vetter wrote:
On Wed, May 23, 2018 at 11:45:00PM +0200, Thomas Hellstrom wrote:
Hi, Noralf.
A couple of issues below:
On 05/23/2018 04:34 PM, Noralf
From: Brian Starkey
Writeback connectors represent writeback engines which can write the
CRTC output to a memory framebuffer. Add a writeback connector type and
related support functions.
Drivers should initialize a writeback connector with
drm_writeback_connector_init()
Hi,
This is v9 of the writeback connector series. Compared to v8 I've
addressed the comments from Eric Anholt, as well as Maarten Lankhorst's
and Daniel Vetter's one on the client capabilities.
Most importantly, I've also realised that Dave Airlie has moved the drm-next
tree to fd.org and went
From: Brian Starkey
Add the WRITEBACK_OUT_FENCE_PTR property to writeback connectors, to
enable userspace to get a fence which will signal once the writeback is
complete. It is not allowed to request an out-fence without a
framebuffer attached to the connector.
A timeline
Due to the fact that writeback connectors behave in a special way
in DRM (they always report being disconnected) we might confuse some
userspace. Add a client capability for writeback connectors that will
filter them out for clients that don't understand the capability.
Changelog:
- only accept
https://bugs.freedesktop.org/show_bug.cgi?id=106597
--- Comment #31 from taij...@posteo.de ---
Created attachment 139740
--> https://bugs.freedesktop.org/attachment.cgi?id=139740=edit
the promised dmesg output with the patch
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=106597
--- Comment #30 from taij...@posteo.de ---
Created attachment 139739
--> https://bugs.freedesktop.org/attachment.cgi?id=139739=edit
patch that seems to fix things for me
OK, going with Lukas' discovery, I have rebuild my kernel from
On 24/05/18 16:54, Tony Lindgren wrote:
> * Tomi Valkeinen [180524 08:00]:
>>
>> On 24/05/18 01:03, Tony Lindgren wrote:
>>> Hi all,
>>>
>>> I bisected the n900 LCD issue to commit 24aac6011f70 ("drm: omapdrm:
>>> sdi: Allocate the sdi private data structure
https://bugs.freedesktop.org/show_bug.cgi?id=106597
--- Comment #29 from taij...@posteo.de ---
So a patch to try would look like:
-static inline bool snd_hda_sync_power_state(struct hda_codec *codec,
+static unsigned int snd_hda_sync_power_state(struct hda_codec *codec,
??
--
You are
Reviewed-by: Benoit Parrot
Tomi Valkeinen wrote on Thu [2018-May-24 10:58:25
+0300]:
>
> On 24/05/18 01:03, Tony Lindgren wrote:
> > Hi all,
> >
> > I bisected the n900 LCD issue to commit 24aac6011f70 ("drm: omapdrm:
> > sdi: Allocate the sdi private
https://bugs.freedesktop.org/show_bug.cgi?id=106597
--- Comment #28 from Lukas Wunner ---
Maybe a revert isn't necessary, I think I've spotted the problem:
+static inline bool snd_hda_sync_power_state(struct hda_codec *codec,
... should be unsigned int.
--
https://bugs.freedesktop.org/show_bug.cgi?id=106597
--- Comment #27 from Lukas Wunner ---
Okay the real culprit seems to be commit 3b5b899ca67d ("ALSA: hda: Make use of
core codec functions to sync power state"):
https://git.kernel.org/linus/3b5b899ca67d
If you revert that,
Hi Dave,
Last feature request for 4.18. Mostly vega20 support.
- Vega20 support
- clock and powergating for VCN
- misc bug fixes
The following changes since commit 315852b422972e6ebb1dfddaadada09e46a2681a:
drm: rcar-du: Fix build failure (2018-05-17 15:03:40 +1000)
are available in the git
https://bugs.freedesktop.org/show_bug.cgi?id=106639
--- Comment #2 from Michel Dänzer ---
Does
https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-4.18=ebdef28ebbcf767d9fa687acb1d02d97d834c628
help?
--
You are receiving this mail because:
You are the assignee for
On Wed, May 23, 2018 at 7:58 PM, Qiang Yu wrote:
> On Thu, May 24, 2018 at 1:24 AM, Rob Herring wrote:
>> On Fri, May 18, 2018 at 05:27:58PM +0800, Qiang Yu wrote:
>>> From: Lima Project Developers
>>>
>>> Signed-off-by: Qiang
Den 24.05.2018 11.01, skrev Daniel Vetter:
Copypasta mistake.
Fixes: 742547b73d27 ("drm/fb_helper: Create wrappers for blit, copyarea and fillrect
funcs")
Cc: Archit Taneja
Cc: Daniel Vetter
Cc: Gustavo Padovan
Cc:
Am Donnerstag, den 24.05.2018, 10:43 +0200 schrieb Lucas Stach:
> Hi Tomi,
>
> Am Donnerstag, den 24.05.2018, 11:39 +0300 schrieb Tomi Valkeinen:
> > Hi Lucas,
> >
> > On 23/05/18 11:53, Lucas Stach wrote:
> >
> > > > With each run, I can see buffers being left lying around,
> > > > visible
> >
On Fri, 11 May 2018, Dhinakaran Pandiyan wrote:
> Entry corresponding to 220 us setup time was missing. I am not aware of
> any specific bug this fixes, but this could potentially result in enabling
> PSR on a panel with a higher setup time requirement than
https://bugs.freedesktop.org/show_bug.cgi?id=106597
--- Comment #26 from Lukas Wunner ---
So hda_call_codec_suspend() tries to set the codec's power state to D3 by
calling hda_set_power_state(). The return value of that is the 32 bit response
detailed on page 151 ff. of the HDA
On Wed, May 23, 2018 at 03:05:35PM +0530, Souptick Joarder wrote:
> On Mon, May 14, 2018 at 9:56 PM, Daniel Vetter wrote:
> > On Thu, May 10, 2018 at 02:51:38PM -0400, Sean Paul wrote:
> >> On Thu, May 10, 2018 at 07:58:11PM +0530, Souptick Joarder wrote:
> >> > Hi Sean,
> >> >
>
On Thu, May 24, 2018 at 5:41 PM, Christian König
wrote:
> Am 24.05.2018 um 11:24 schrieb Qiang Yu:
>>
>> On Thu, May 24, 2018 at 2:46 PM, Christian König
>> wrote:
>> [SNIP]
>>>
>>> Because of this we have a separate tracking in amdgpu so that
Hi Kieran,
Thank you for the patch.
On Thursday, 3 May 2018 16:36:21 EEST Kieran Bingham wrote:
> Calculate the top and bottom fields for the interlaced frames and
> utilise the extended display list command feature to implement the
> auto-field operations. This allows the DU to update the VSP2
Hi all,
I bisected the n900 LCD issue to commit 24aac6011f70 ("drm: omapdrm:
sdi: Allocate the sdi private data structure dynamically"). Reverting
this patch makes LCD work for me again on n900.
Any ideas?
Regards,
Tony
___
dri-devel mailing list
On Wed, May 23, 2018 at 10:48:15AM +0200, Daniel Vetter wrote:
> On Tue, May 22, 2018 at 09:27:07AM +0100, Russell King wrote:
> > On Tue, May 22, 2018 at 10:53:49AM +1000, Dave Airlie wrote:
> > > Sorry I missed this, just fell between the cracks,
> > >
> > > Any reason you can't/don't use git
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Ref-> commit 1c8f422059ae ("mm: change return type to vm_fault_t")
DP firmware uses fixed phy config values to do training, but some
boards need to adjust these values to fit for their unique hardware
design. So get phy config values from dts and use software link training
instead of relying on firmware, if software training fail, keep firmware
training as a
On 2018-05-23 14:38, Andrzej Hajda wrote:
> On 23.05.2018 12:46, Peter Rosin wrote:
>> On 2018-05-23 11:39, Andrzej Hajda wrote:
>>
>> *snip*
>>
>>> Panels are managed by dsi host only if dsi host implements it, and it is
>>> up to dsi host author, it is not mandatory. The only case I am aware of
the phy config values used to fix in dp firmware, but some boards
need change these values to do training and get the better eye diagram
result. So support that in phy driver.
Signed-off-by: Chris Zhong
Signed-off-by: Lin Huang
---
Changes in v2:
-
On Wed, May 23, 2018 at 10:53:33AM +0200, Daniel Vetter wrote:
> On Sun, May 20, 2018 at 09:22:31AM +0300, Haneen Mohammed wrote:
> > On Wed, May 16, 2018 at 08:56:21PM -0300, Rodrigo Siqueira wrote:
> > > This commit adds the essential infrastructure for around CRTCs which
> > > is composed of: a
On Mon, May 14, 2018 at 9:56 PM, Daniel Vetter wrote:
> On Thu, May 10, 2018 at 02:51:38PM -0400, Sean Paul wrote:
>> On Thu, May 10, 2018 at 07:58:11PM +0530, Souptick Joarder wrote:
>> > Hi Sean,
>> >
>> > On Mon, Apr 16, 2018 at 8:32 PM, Souptick Joarder
On Wed, May 23, 2018 at 2:19 PM, Daniel Vetter wrote:
> On Mon, May 21, 2018 at 10:27:44AM +0530, Souptick Joarder wrote:
>> On Thu, May 10, 2018 at 7:18 PM, Souptick Joarder
>> wrote:
>> > On Wed, Apr 25, 2018 at 10:29 AM, Souptick Joarder
> A non-fatal signal being delivered to a task which is
> in the middle of a page fault may well end up in an
> infinite loop, attempting to handle the page fault and
> failing forever.
>
> On seeing NOPAGE, the fault handler believes the PTE
> is in the page table, so does nothing before it
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Ref-> commit 1c8f422059ae ("mm: change return type to vm_fault_t")
On 2018-05-22 17:03, Peter Rosin wrote:
> On 2018-05-22 11:45, Andrzej Hajda wrote:
>> On 22.05.2018 09:36, Peter Rosin wrote:
>>> On 2018-05-22 08:29, Andrzej Hajda wrote:
On 21.05.2018 23:56, Peter Rosin wrote:
> On 2018-05-21 11:21, Andrzej Hajda wrote:
>> On 21.05.2018 10:53,
This beats the heuristic that the connector is involved in what format
should be output for cases where this fails.
E.g. if there is a bridge that changes format between the encoder and the
connector, or if some of the RGB pins between the lcd controller and the
encoder are not routed on the PCB.
On 23/05/18 13:36, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko
>
> Building for a 32-bit target results in warnings from casting
> between a 32-bit pointer and a 64-bit integer. Fix the warnings
> by casting those pointers to uintptr_t first.
On Wed, May 23, 2018 at 11:15:18AM +0200, Daniel Vetter wrote:
> On Mon, May 21, 2018 at 10:04:23PM -0300, Rodrigo Siqueira wrote:
> > This series of patches add a centralized initialization mechanism, a
> > single CRTC with a plane, an encoder, and extra module information.
> >
> > Changes in
On Wed, May 23, 2018 at 10:24 AM, Rob Herring wrote:
> On Fri, May 18, 2018 at 05:27:58PM +0800, Qiang Yu wrote:
>> From: Lima Project Developers
>>
>> Signed-off-by: Qiang Yu
>> Signed-off-by: Heiko Stuebner
On Wed, May 23, 2018 at 5:36 PM, Ben Skeggs wrote:
> On Thu, May 24, 2018 at 8:48 AM, Kees Cook wrote:
>> On Thu, Apr 26, 2018 at 4:25 PM, Kees Cook wrote:
>>> On Thu, Mar 15, 2018 at 7:05 PM, Ben Skeggs
On Thu, 24 May 2018, John Sledge wrote:
> I was able to update my kernel to 4.6 which has the DRM_DP_AUX_CHARDEV
> in the Kconfig file linux-4.6\drivers\gpu\drm. Though I also
> add DRM_DP_AUX_CHARDEV=y in kernel config. When invoke uname -r, I
> could see that the kernel
https://bugs.freedesktop.org/show_bug.cgi?id=106597
--- Comment #24 from Lukas Wunner ---
(In reply to taijian from comment #22)
> $ grep . /sys/bus/hdaudio/devices/hdaudioC1D0/widgets/*/power_caps
> /sys/bus/hdaudio/devices/hdaudioC1D0/widgets/01/power_caps:0xc009
The ChromeOS Embedded Controller can expose a CEC bus, this patch add the
driver for such feature of the Embedded Controller.
This driver is part of the cros-ec MFD and will be add as a sub-device when
the feature bit is exposed by the EC.
The controller will only handle a single logical address
Hi Kieran,
Thank you for the patch.
On Thursday, 3 May 2018 16:36:19 EEST Kieran Bingham wrote:
> Extended display list headers allow pre and post command lists to be
> executed by the VSP pipeline. This provides the base support for
> features such as AUTO_FLD (for interlaced support) and
On Wed, May 23, 2018 at 04:34:09PM +0200, Noralf Trønnes wrote:
> This switches the CMA helper drivers that use its fbdev emulation over
> to the generic fbdev emulation. It's the first phase of using generic
> fbdev. A later phase will use DRM client callbacks for the
> lastclose/hotplug/remove
Hi Kieran,
Thank you for the patch.
On Thursday, 3 May 2018 16:36:16 EEST Kieran Bingham wrote:
> If there is an error allocating a display list within a DLM object
> the existing display lists are not free'd, and neither is the DL body
> pool.
>
> Use the existing vsp1_dlm_destroy() function
Having a 16 byte mkbp event size makes it possible to send CEC
messages from the EC to the AP directly inside the mkbp event
instead of first doing a notification and then a read.
Signed-off-by: Stefan Adolfsson
Signed-off-by: Neil Armstrong
On Thu, May 24, 2018 at 11:25:04AM +0200, Thomas Hellstrom wrote:
> On 05/24/2018 10:32 AM, Daniel Vetter wrote:
> > On Wed, May 23, 2018 at 11:45:00PM +0200, Thomas Hellstrom wrote:
> > > Hi, Noralf.
> > >
> > > A couple of issues below:
> > >
> > > On 05/23/2018 04:34 PM, Noralf Trønnes wrote:
Hi Kieran,
Thank you for the patch.
On Thursday, 3 May 2018 16:36:20 EEST Kieran Bingham wrote:
> VSPD and VSP-DL devices can provide extended display lists supporting
> extended command display list objects.
>
> These extended commands require their own dma memory areas for a header
> and body
Hi Kieran,
Thank you for the patch.
On Thursday, 3 May 2018 16:36:22 EEST Kieran Bingham wrote:
> Use the newly exposed VSP1 interface to enable interlaced frame support
> through the VSP1 lif pipelines.
s/lif/LIF/
>
> Signed-off-by: Kieran Bingham
>
On 05/24/2018 10:32 AM, Daniel Vetter wrote:
On Wed, May 23, 2018 at 11:45:00PM +0200, Thomas Hellstrom wrote:
Hi, Noralf.
A couple of issues below:
On 05/23/2018 04:34 PM, Noralf Trønnes wrote:
This the beginning of an API for in-kernel clients.
First out is a way to get a framebuffer
Hi Kieran,
Thank you for the patch.
On Thursday, 3 May 2018 16:36:18 EEST Kieran Bingham wrote:
> Header mode display lists are now supported on all WPF outputs. To
> support extended headers and auto-fld capabilities for interlaced mode
> handling only header mode display lists can be used.
>
1 - 100 of 204 matches
Mail list logo