Dear Thierry,
Could you check these patches?
I think this patches have accumulated enough dust.
If you have a another opinion, please tell me.
Best regards,
Hoegeun
On 04/18/2017 05:40 PM, Hoegeun Kwon wrote:
Hi all,
The purpose of this patch is add support for s6e3hf2 AMOLED panel on
the TM2
https://bugzilla.kernel.org/show_bug.cgi?id=194761
--- Comment #9 from Jean Delvare (jdelv...@suse.de) ---
Sorry there was a missing digit in the commit ID, I obviously meant
f8d9422ef80c ("drm/amdgpu: update tile table for oland/hainan".)
--
You are receiving this mail because:
You are watching
On 05/16/2017 01:48 AM, Krzysztof Kozlowski wrote:
On Wed, Mar 08, 2017 at 01:54:11PM +0900, Hoegeun Kwon wrote:
The OF graph is not needed because the panel is a child of dsi. Remove
the ports node in DSI node.
Signed-off-by: Hoegeun Kwon
Reviewed-by: Andrzej Hajda
Reviewed-by: Andi Shyti
-
https://bugzilla.kernel.org/show_bug.cgi?id=194761
Jean Delvare (jdelv...@suse.de) changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolu
On 05/17/2017 05:05 PM, Daniel Vetter wrote:
On Wed, May 17, 2017 at 10:56:25AM +0530, Archit Taneja wrote:
Hi,
On 05/16/2017 08:14 PM, Archit Taneja wrote:
On 5/13/2017 12:40 AM, Gustavo Padovan wrote:
From: Gustavo Padovan
Add support to async updates of cursors by using the new atomi
On 18.05.2017 13:10, Jani Nikula wrote:
> Face the fact, there are Display Port sink and branch devices out there
> in the wild that don't follow the Display Port specifications, or they
> have bugs, or just otherwise require special treatment. Start a common
> quirk database the drivers can query
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in:
drivers/gpu/drm/i915/intel_dp_mst.c
between commit:
f424f55e3177 ("drm/i915: Track MST link bandwidth")
from the drm tree and commit:
3d65a735d834 ("drm/i915/mst: use max link not sink lane count")
from the drm-i
On 05/17, Maxime Ripard wrote:
> So far, divider_round_rate only considers the parent clock returned by
> clk_hw_get_parent.
>
> This works fine on clocks that have a single parents, this doesn't work on
> muxes, since we will only consider the first parent, while other parents
> may totally be ab
https://bugs.freedesktop.org/show_bug.cgi?id=99851
--- Comment #34 from Michel Dänzer ---
For any commits that you can't test, run "git bisect skip". Eventually, it will
either identify the first bad commit or specify the minimum set of candidates.
--
You are receiving this mail because:
You ar
https://bugs.freedesktop.org/show_bug.cgi?id=99851
Michel Dänzer changed:
What|Removed |Added
Attachment #131410|text/x-log |text/plain
mime type|
Now that we have a callback to check if bridge supports a given mode
we can use it in Synopsys Designware HDMI bridge so that we restrict
the number of probbed modes to the ones we can actually display.
Also, there is no need to use mode_fixup() callback as mode_valid()
will handle the mode valida
This fixes the DRM_IOCTL_MODE_GETFB ioctl for cirrus so that it
returns an actual handle instead of failing with ENODEV.
Tested in a QEMU VM with "-vga cirrus" by running this script:
https://chromium.googlesource.com/chromiumos/third_party/autotest/+/master/client/bin/screenshot.py
Implementati
This patches makes use of the new mode_valid() callbacks introduced
previously to validate the full video pipeline when modesetting.
This calls the connector->mode_valid(), encoder->mode_valid(),
bridge->mode_valid() and crtc->mode_valid() so that we can
make sure that the mode will be accepted in
On Thu, 2017-05-18 at 14:10 +0300, Jani Nikula wrote:
> Face the fact, there are Display Port sink and branch devices out there
> in the wild that don't follow the Display Port specifications, or they
> have bugs, or just otherwise require special treatment. Start a common
> quirk database the driv
Introduce a new helper function which calls mode_valid() callback
for all bridges in an encoder chain.
Signed-off-by: Jose Abreu
Reviewed-by: Daniel Vetter
Cc: Carlos Palminha
Cc: Alexey Brodkin
Cc: Ville Syrjälä
Cc: Daniel Vetter
Cc: Dave Airlie
Cc: Andrzej Hajda
Cc: Archit Taneja
Cc: La
Now that we have a callback to check if crtc and encoder supports a
given mode we can use it in vc4 so that we restrict the number of
probbed modes to the ones we can actually display.
Also, remove the mode_fixup() calls as these are no longer needed
because mode_valid() will be called before.
NO
Now that we have a callback to check if bridge supports a given mode
we can use it in Analogix bridge so that we restrict the number of
probbed modes to the ones we can actually display.
Also, there is no need to use mode_fixup() callback as mode_valid()
will handle the mode validation.
NOTE: Onl
Now that we have a callback to check if crtc supports a given mode
we can use it in malidp so that we restrict the number of probbed
modes to the ones we can actually display.
Also, remove the mode_fixup() callback as this is no longer needed
because mode_valid() will be called before.
NOTE: Not
From: Wei Yongjun
Fix the return value check which testing the wrong variable.
Signed-off-by: Wei Yongjun
---
drivers/gpu/drm/i915/selftests/i915_sw_fence.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/selftests/i915_sw_fence.c
b/drivers/gpu/drm
Now that we have a callback to check if crtc supports a given mode
we can use it in arcpgu so that we restrict the number of probbed
modes to the ones we can actually display.
This is specially useful because arcpgu crtc is responsible to set
a clock value in the commit() stage but unfortunatelly
This series is a follow up from the discussion at [1]. We start by
introducing crtc->mode_valid(), encoder->mode_valid() and
bridge->mode_valid() callbacks which will be used in followup
patches and also by cleaning the documentation a little bit. This
patch is available at [2] and the series depen
This changes the connector probe helper function to use the new
encoder->mode_valid(), bridge->mode_valid() and crtc->mode_valid()
helper callbacks to validate the modes.
The new callbacks are optional so the behaviour remains the same
if they are not implemented. If they are, then the code loops
On Wed, 2017-05-17 at 14:04 -0700, Puthikorn Voravootivat wrote:
>
> On Wed, May 17, 2017 at 1:09 PM, Pandiyan, Dhinakaran
> wrote:
>
>
> From: Puthikorn Voravootivat [put...@google.com] on behalf of
> Puthikorn Voravootiva
Add a new helper to call crtc->mode_valid, connector->mode_valid
and encoder->mode_valid callbacks.
Suggested-by: Ville Syrjälä
Signed-off-by: Jose Abreu
Reviewed-by: Daniel Vetter
Reviewed-by: Andrzej Hajda
Cc: Carlos Palminha
Cc: Alexey Brodkin
Cc: Ville Syrjälä
Cc: Daniel Vetter
Cc: Dav
Now that we have a callback to check if crtc supports a given mode
we can use it in atmel-hlcdc so that we restrict the number of probbed
modes to the ones we can actually display.
Also, remove the mode_fixup() callback as this is no longer needed
because mode_valid() will be called before.
NOTE:
On 05/08, Eric Anholt wrote:
> This is required for the panel to work on bcm911360, where CLCDCLK is
> the fixed 200Mhz AXI41 clock. The rate set is still passed up to the
> CLCDCLK, for platforms that have a settable rate on that one.
>
> v2: Set SET_RATE_PARENT (caught by Linus Walleij), depend
https://bugzilla.kernel.org/show_bug.cgi?id=195321
--- Comment #3 from Jimi (jimijames.b...@gmail.com) ---
Hello? I still can't upgrade my kernel until this gets fixed.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_
Sorry about the spam, but the previous reply was intended for
[RFC v3 7/8] drm/vc4: update cursors asynchronously through atomic
On 2017-05-18 06:52 PM, Robert Foss wrote:
Hey,
I ran the series on a RPi2 and the cursor seems to behave correctly.
Tested-by: Robert Foss
On 2017-04-09 08:24 PM
Hey,
I just tested this patch on a RPi2, and the cursor behaves correctly with no
unexpected errors.
Tested-by: Robert Foss
On 2017-05-12 03:10 PM, Gustavo Padovan wrote:
From: Gustavo Padovan
Add support to async updates of cursors by using the new atomic
interface for that. Basically wh
Hey,
I ran the series on a RPi2 and the cursor seems to behave correctly.
Tested-by: Robert Foss
On 2017-04-09 08:24 PM, Gustavo Padovan wrote:
From: Gustavo Padovan
Add support to async updates of cursors by using the new atomic
interface for that. Basically what this commit does is do wha
On Fri, May 12, 2017 at 04:56:28PM +0200, Philippe CORNU wrote:
> This patch adds documentation of device tree bindings for the STM32
> DSI host driver based on the Synopsys DW MIPI DSI driver from Rockchip.
>
> Signed-off-by: Philippe CORNU
> ---
> .../devicetree/bindings/display/st,stm32-ltdc.
This patch removes old code related to the old api and transforms the
functions for the new api. It also adds the .write and .read operations.
Signed-off-by: Oscar Salvador
Reviewed-by: Martin Peres
---
drivers/gpu/drm/nouveau/nouveau_hwmon.c | 844 ++--
1 file chang
This patch replaces the symbolic permissions with the numeric ones.
Signed-off-by: Oscar Salvador
Reviewed-by: Martin Peres
---
drivers/gpu/drm/nouveau/nouveau_hwmon.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_hwmon.c
b/drive
This patch creates a special group attributes for attrs like "*auto_point*".
We check if we have support for them, and if we do, we gather them all in
an attribute_group's structure which is the parameter regarding special groups
of hwmon_device_register_with_info
We also do the same for pwm_min/ma
This patch introduces the nouveau_hwmon_ops structure, sets up
.is_visible and .read_string operations and adds all the functions
for these operations.
This is also a preparation for the next patches, where most of the
work is being done.
This code doesn't interacture with the old one.
It's just to
This is a preparation for the next patches. It just adds the sensors with
their possible configurable settings and then fills the struct
hwmon_channel_info
with all this information.
Signed-off-by: Oscar Salvador
Reviewed-by: Martin Peres
---
drivers/gpu/drm/nouveau/nouveau_hwmon.c | 72 ++
This v8 fixes removes dummy functions which only had a return and moves the code
into the switch statements.
Versions:
v1 -> v2:
* Keep temp attrs as read only
v2 -> v3:
* Code fix-ups: struct and string as const and add return within switch
due to fallthrough
* Ad
https://bugs.freedesktop.org/show_bug.cgi?id=99851
--- Comment #33 from erhar...@mailbox.org ---
Created attachment 131411
--> https://bugs.freedesktop.org/attachment.cgi?id=131411&action=edit
bisect kernel .config
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=99851
--- Comment #32 from erhar...@mailbox.org ---
Created attachment 131410
--> https://bugs.freedesktop.org/attachment.cgi?id=131410&action=edit
incomplete bisect.log
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=99851
--- Comment #31 from erhar...@mailbox.org ---
Unfortunately my bisect efforts came to a halt as the current kernel won't
boot. Early OpenFirmware boot console shows "Kernel panic - not syncing:
Couldn't allocate pmd pagetable caches". The G5 freez
Implement CTM color management property for OMAP CRTC using DSS
overlay manager's Color Phase Rotation matrix. The CPR matrix does not
exactly match the CTM property documentation. On DSS the CPR matrix is
applied after gamma table look up. However, it seems stupid to add a
custom property just for
Daniel Vetter writes:
> On Wed, May 17, 2017 at 03:43:18PM -0300, Gabriel Krisman Bertazi wrote:
>> Daniel Vetter writes:
>>
>> > On Thu, Apr 20, 2017 at 09:38:19PM -0300, Gabriel Krisman Bertazi wrote:
>> >> While reading drm_for_each_connector_iter, I noticed a mention to
>> >> drm_connector_
Mike Galbraith writes:
> On Mon, 2017-05-08 at 16:48 -0300, Gabriel Krisman Bertazi wrote:
>
>> Thanks for reporting this. Can you confirm the following patch prevents
>> the issue?
>
> Nope, it still gripes.
Oops... Thanks for checking. The following patch fixes the issue for
me. Can you ple
This fixes the DRM_IOCTL_MODE_GETFB ioctl for cirrus so that it
returns an actual handle instead of failing with ENODEV.
Tested in a QEMU VM with "-vga cirrus" by running this script:
https://chromium.googlesource.com/chromiumos/third_party/autotest/+/master/client/bin/screenshot.py
Implementati
There is no reason why the name field should not be const, but
several why it should. The struct should only be used by
drm_property_create_enum() and there the name-field from the struct
is passed to drm_property_add_enum(), which takes a const char * as
a parameter.
Signed-off-by: Jyri Sarha
--
Add a standard optional properties to support different non RGB color
encodings in DRM planes. COLOR_ENCODING select the supported non RGB
color encoding, for instance ITU-R BT.709 YCbCr. COLOR_RANGE selects
the value ranges within the selected color encoding. The properties
are stored to drm_plane
Changes since v3 RFC version:
- Add: "drm: Add const to name field declaration in struct drm_prop_enum_list"
- Fix typos found by Eric Engestrom
- Restructure kernel doc
- Add consts to name sting tables
- Loop variables from unsigned to signed int
- Use len variable to index temporary enum_l
From: Ville Syrjälä
drm_atomic_set_mode_for_crtc() doesn't modify the passed mode, so let's
make it const.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/drm_atomic.c | 2 +-
include/drm/drm_atomic.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/d
From: Ville Syrjälä
Make the mode used for load detection const, and adjust all relevant
functions to accept a const mode.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/intel_display.c | 12 ++--
drivers/gpu/drm/i915/intel_drv.h | 2 +-
2 files changed, 7 insertions(+), 7
Nicolai Stange reports the following oops which is caused by
dereferencing rdev->pdev before it's subsequently set by
radeon_device_init(). Fix it.
BUG: unable to handle kernel NULL pointer dereference at 07cb
IP: radeon_driver_load_kms+0xeb/0x230 [radeon]
PGD 0
P4D 0
Oops:
Signed-off-by: Jeff Smith
---
All of the encoder_info_frame's info packets are initialized to invalid
in resource_build_info_frame except for spd. This appears to be simply
an oversight.
drivers/gpu/drm/amd/display/dc/core/dc_resource.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/driver
https://bugs.freedesktop.org/show_bug.cgi?id=101029
--- Comment #22 from Craig ---
in that case, when will this patch be applied permanently in a kernel versus
having to use the patch? I will be attempting to apply the patch soon and
verify as well on the Ubuntu side.
--
You are receiving this
Philippe CORNU writes:
> Add the bridge support, used by DSI host and HDMI/LVDS bridges.
>
> Signed-off-by: Philippe CORNU
> @@ -987,19 +1024,36 @@ static struct drm_panel *ltdc_get_panel(struct
> drm_device *ddev)
>
> port = of_graph_get_remote_port_parent(entity);
>
https://bugs.freedesktop.org/show_bug.cgi?id=101029
--- Comment #21 from Jan Vesely ---
I have the same problem on carrizo+iceland nb (reported at [0,1]).
I can confirm that the linked patch applied on top of 4.10.x fixes boot, and
the machine can run 3d applications (tested glxgears) on both GP
Reviewed-by: Eric Huang
On 2017-05-16 10:42 AM, Dan Carpenter wrote:
Smatch complains about a signedness bug here:
vega10_hwmgr.c:4202 vega10_force_clock_level()
warn: always true condition '(i >= 0) => (0-u32max >= 0)'
Fixes: 7b52db39a4c2 ("drm/amd/powerplay: fix bug sclk/mc
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/i810/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/i810/Makefile b/drivers/gpu/drm/i810/Makefile
index 43844
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/mga/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/mga/Makefile b/drivers/gpu/drm/mga/Makefile
index 6068478.
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/sis/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/sis/Makefile b/drivers/gpu/drm/sis/Makefile
index 441c061.
From: Kuninori Morimoto
ALSA SoC needs to know connected DAI ID for probing.
It is not a big problem if device/driver was only for sound,
but getting DAI ID will be difficult if device includes both
Video/Sound, like HDMI.
To solve this issue, this patch adds new .get_dai_id callback
on hdmi_cod
Many Makefiles needed to add -Iinclude/drm as an include path,
but the right thing to do is to include headers in the form
#include
This series fixes the source files, then rip off -Iinclude/drm flags.
V3: rebased on commit bb2af9bda33 (drm-misc-next)
Masahiro Yamada (16):
drm/vc4: fix in
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
While we are here, use <...> instead of "..." for include/linux/*.h
and include/sound/*.h headers too.
Signed-off-by: Masahiro Yamada
---
Changes in v3:
- Rebase
drivers/gpu/drm/vc4/Makefile
Hi Daniel,
2017-05-17 21:40 GMT+09:00 Daniel Vetter :
> On Mon, Apr 24, 2017 at 01:50:33PM +0900, Masahiro Yamada wrote:
>> Include instead of relative path from include/drm, then
>> remove the -Iinclude/drm compiler flag.
>>
>> While we are here, use <...> instead of "..." for include/linux/*.h
From: Kuninori Morimoto
ALSA SoC needs to know connected DAI ID for detecting.
It is not a big problem if device/driver was only for sound,
but getting DAI ID will be difficult if device includes both
Video/Sound, like HDMI.
To solve this issue, this patch adds new snd_soc_get_dai_id() and
its r
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/vgem/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/vgem/Makefile b/drivers/gpu/drm/vgem/Makefile
index bfcde
Em Fri, 5 May 2017 16:21:10 +0100
Kieran Bingham escreveu:
> Currently we process page flip events on every display interrupt,
> however this does not take into consideration the processing time needed
> by the VSP1 utilised in the pipeline.
>
> Register a callback with the VSP driver to obtain
On 18/05/2017 at 14:35:21 +0200, Boris Brezillon wrote:
> drm_of_find_panel_or_bridge() is expecting np to point to the encoder
> node, not the bridge or panel this encoder is feeding.
> Moreover, the endpoint parameter passed to drm_of_find_panel_or_bridge()
> is always set to zero, which prevents
Add COMPILE_TEST for the compilation test coverage.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/stm/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/stm/Kconfig b/drivers/gpu/drm/stm/Kconfig
index 2c4817f..722ad11 100644
--- a/drivers/gpu/drm/st
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/tdfx/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/tdfx/Makefile b/drivers/gpu/drm/tdfx/Makefile
index 0379f
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/i2c/Makefile | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/gpu/drm/i2c/Makefile b/drivers/gpu/drm/i2c/Makefile
index 43aa33
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/r128/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/r128/Makefile b/drivers/gpu/drm/r128/Makefile
index 1cc72
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/omapdrm/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/omapdrm/Makefile b/drivers/gpu/drm/omapdrm/Makefile
in
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/vmwgfx/Makefile | 3 ---
drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c | 3 ++-
drivers/gpu/drm/vmwgfx/vmwgfx_context.c | 3
On 18.05.2017 14:42, Dmitry Osipenko wrote:
On 20.03.2017 21:44, Mikko Perttunen wrote:
...
struct host1x_channel *host1x_channel_request(struct device *dev)
{
struct host1x *host = dev_get_drvdata(dev->parent);
+ struct host1x_channel_list *chlist = &host->channel_list;
On 18.05.2017 14:55, Mikko Perttunen wrote:
> On 18.05.2017 14:42, Dmitry Osipenko wrote:
>> On 20.03.2017 21:44, Mikko Perttunen wrote:
>>> ...
>>> struct host1x_channel *host1x_channel_request(struct device *dev)
>>> {
>>> struct host1x *host = dev_get_drvdata(dev->parent);
>>> +struct
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/savage/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/savage/Makefile b/drivers/gpu/drm/savage/Makefile
index
Hi Mark, Archit
These supports HDMI sound for Codec.
Now, SYNOPSYS dw-hdmi-i2s-audio driver is supporting HDMI I2S
and is using hdmi-codec driver.
Now, ALSA SoC supports OF-graph DT style, this means V4L2/ALSA SoC
can share same DT bindings.
But 1 issue is that ALSA SoC side needs to adjust port
Use <...> notation to include headers located in include/linux.
While we are here, tweak the includes order a bit to sort them
alphabetically.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/amd/powerplay/hwmgr/hwmgr.c| 4 ++--
drivers/gpu/drm/amd/powerplay/hwmgr/pp_acpi.c | 2 +
On 20.03.2017 21:44, Mikko Perttunen wrote:
> This is largely a rewrite of the Host1x channel allocation
> code in channel.c, bringing several changes:
>
> - The previous code could deadlock due to an interaction
> between the 'reflock' mutex and CDMA timeout handling.
> This gets rid of the m
From: Kuninori Morimoto
ALSA SoC needs to know connected DAI ID for probing.
It is not a big problem if device/driver was only for sound,
but getting DAI ID will be difficult if device includes both
Video/Sound, like HDMI.
To solve this issue, this patch adds new .get_dai_id callback
on hdmi_cod
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/udl/Makefile | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/gpu/drm/udl/Makefile b/drivers/gpu/drm/udl/Makefile
index 195bc
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/gma500/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/gma500/Makefile b/drivers/gpu/drm/gma500/Makefile
index
From: Kuninori Morimoto
ALSA SoC needs to know connected DAI ID for detecting.
It is not a big problem if device/driver was only for sound,
but getting DAI ID will be difficult if device includes both
Video/Sound, like HDMI.
To solve this issue, this patch adds new snd_soc_get_dai_id() and
its r
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/virtio/Makefile | 2 --
drivers/gpu/drm/virtio/virtgpu_debugfs.c | 2 +-
drivers/gpu/drm/virtio/virtgpu_drv.c |
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/via/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/via/Makefile b/drivers/gpu/drm/via/Makefile
index d59e258.
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/stm/Makefile | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/gpu/drm/stm/Makefile b/drivers/gpu/drm/stm/Makefile
index e114d4
From: Kuninori Morimoto
DesignWare HDMI driver (= dw-hdmi) is supporting HDMI sound, and its
probe function was calling sound binding function multiple times as
same HDMI device different port.
Because of this behavior, commit 9731f82d601 ("ASoC: hdmi-codec: enable
multi probe for ...") was add
2017-05-11 5:51 GMT+03:00 Michel Dänzer :
> On 11/05/17 04:33 AM, Tommi Rantala wrote:
>> Complete kernel log:
>> http://termbin.com/dzy5
>>
>> [ 249.952546] [ cut here ]
>> [ 249.952593] WARNING: CPU: 5 PID: 0 at
>> /home/ttrantal/git/linux/drivers/gpu/drm/drm_irq.c:1195
vmwgfx part: Reviewed-by: Sinclair Yeh
On Wed, May 17, 2017 at 09:39:11PM -0400, Robert Foss wrote:
> Add DRM_MODE_ROTATE_ and DRM_MODE_REFLECT_ defines to the UAPI
> as a convenience.
>
> Ideally the DRM_ROTATE_ and DRM_REFLECT_ property ids are looked up
> through the atomic API, but realizing
https://bugs.freedesktop.org/show_bug.cgi?id=100437
--- Comment #8 from Öyvind Saether ---
Motherboard: MSI-A88X-G45-GAMING
APU: AMD A8-7600
Graphics card: MSI RX 470 8GB
Kernel: 4.11.0-2.fc26.x86_64
Screens: 3 (1080 1440 1080)
I can confirm that on cold boot I too get AMD-Vi: Event logged and
I
On Thu, May 18, 2017 at 10:16:38AM +0200, Christian König wrote:
> Am 17.05.2017 um 14:23 schrieb Michal Hocko:
> > As it turned out my allyesconfig on x86_64 wasn't sufficient and 0day
> > build machinery found a failure on arm architecture. It was clearly a
> > typo. Now I have pushed this to my
Gentle ping on this.
Thanks,
Liviu
Hi Dave,
I'm not sure what is the best tree to target this, probably v4.12-rc1 if it
is too late to make it into the pull request for this merge window. Just a
patch that has been in linux-next for a very long time due to lack of feedback
and me going on holid
On 05/18/2017 04:10 AM, Jani Nikula wrote:
Face the fact, there are Display Port sink and branch devices out there
in the wild that don't follow the Display Port specifications, or they
have bugs, or just otherwise require special treatment. Start a common
quirk database the drivers can query b
Hi Dave,
2 fixes for you, one fixes a link error that seems to have been lurking for a
while, but aggrevated by rc1. The second patch fixes a bug introduced in the
find_panel_or_bridge cleanup set.
drm-misc-fixes-2017-05-18:
Driver Changes:
- host1x: Fix link error when host1x is built-in and iov
On 18 May 2017 at 14:46, Emil Velikov wrote:
> On 18 May 2017 at 13:47, Eric Engestrom wrote:
>
>>> > Yes, I think you should change your build command. It's a shame that
>>> > autotools has this bug, but we'd like to avoid changing our codebase to
>>> > work around these, and in this case, it wo
On Thu, Apr 20, 2017 at 09:47:35AM +0300, Mikko Perttunen wrote:
> Ah, had to forget something :)
>
> Reviewed-by: Mikko Perttunen
Applied to -misc-fixes, thank you
Sean
>
> On 19.04.2017 21:24, Arnd Bergmann wrote:
> > When IOMMU_IOVA is not built-in but host1x is, we get a link error:
> >
On Thu, May 18, 2017 at 02:43:07PM +0200, Alexandre Belloni wrote:
> On 18/05/2017 at 14:35:21 +0200, Boris Brezillon wrote:
> > drm_of_find_panel_or_bridge() is expecting np to point to the encoder
> > node, not the bridge or panel this encoder is feeding.
> > Moreover, the endpoint parameter pass
Hi Archit,
On Thursday 18 May 2017 13:56:19 Archit Taneja wrote:
> On 05/17/2017 12:16 AM, Eric Anholt wrote:
[snip]
> > In terms of physical connections:
> >[15-pin "DSI" connector on 2835]
> >
> > | I2C | DSI
> >
> >/ \SPI |
> >
> > [TS] [Atmel
Hi Eric,
On Tuesday 16 May 2017 11:46:36 Eric Anholt wrote:
[snip]
> In terms of physical connections:
>
>[15-pin "DSI" connector on 2835]
>
> | I2C | DSI
>/ \SPI |
> [TS] [Atmel]--[TC358762]
>\|
> \PWM|
>
On Thu, May 18, 2017 at 02:39:42PM +0100, Colin King wrote:
> From: Colin Ian King
>
> There are two occasions where pointer B is being check for a NULL
> when it should be pointer C instead. Fix these.
>
> Detected by CoverityScan, CID#1436348,1436349 ("Logically Dead Code")
>
> Fixes: 47624cc
https://bugs.freedesktop.org/show_bug.cgi?id=99851
--- Comment #30 from erhar...@mailbox.org ---
The same problem on my machine:
# dmesg | grep -i drm
[ 11.753729] [drm] radeon kernel modesetting enabled.
[ 11.760535] [drm] initializing kernel modesetting (CEDAR 0x1002:0x68F9
0x1787:0x2291 0x
1 - 100 of 134 matches
Mail list logo
