s issue is fixed?
--
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/20160627/982fd82e/attachment.html>
On Mon, 2016-06-27 at 12:20 +0200, Matthias Brugger wrote:
>
> On 06/24/2016 09:27 AM, Bibby Hsieh wrote:
> > Hi Dave,
> >
> > Please consider merging this tag, which contains the v2 MT8173 gamma &
> > dither function patches I sent on 2016-06-17, rebased onto v4.7-rc1. There
> > have been no fu
That constant isn't meant to be used outside of arch mm code
Signed-off-by: Benjamin Herrenschmidt
---
drivers/gpu/drm/drm_memory.c | 2 +-
drivers/gpu/drm/drm_scatter.c | 2 +-
drivers/gpu/drm/drm_vm.c | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/dr
The patch
ASoC: hdmi-codec: callback function will be called with private data
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
te= vgem_gem_dumb_create,
> .dumb_map_offset= vgem_gem_dumb_map,
> +
> + .prime_handle_to_fd = drm_gem_prime_handle_to_fd,
> + .gem_prime_pin = vgem_prime_pin,
> + .gem_prime_export = drm_gem_prime_export,
> + .gem_prime_get_sg_table = vgem_prime_get_sg_table,
> + .gem_prime_vmap = vgem_prime_vmap,
> + .gem_prime_vunmap = vgem_prime_vunmap,
> + .gem_prime_mmap = vgem_prime_mmap,
> +
> .name = DRIVER_NAME,
> .desc = DRIVER_DESC,
> .date = DRIVER_DATE,
> --
> 2.8.1
>
>
Acked-by: Zach Reizner
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160627/7e4066b1/attachment.html>
From: Gustavo Padovan
Create sync_file->fence to abstract the type of fence we are using for
each sync_file. If only one fence is present we use a normal struct fence
but if there is more fences to be added to the sync_file a fence_array
is created.
This change cleans up sync_file a bit. We don'
From: Gustavo Padovan
As the array of fence callbacks held by an active struct fence_array
each has a reference to the struct fence_array, when the owner of the
fence_array is freed it must dispose of the callback references before
it can free the fence_array. This can not happen simply during
fe
From: Gustavo Padovan
Add helper to check if fence is array.
Cc: Chris Wilson
Cc: Christian König
Signed-off-by: Gustavo Padovan
---
include/linux/fence-array.h | 10 ++
1 file changed, 10 insertions(+)
diff --git a/include/linux/fence-array.h b/include/linux/fence-array.h
index 86
From: Gustavo Padovan
Hi all,
This is an attempt to improve fence support on Sync File. The basic idea
is to have only sync_file->fence and store all fences there, either as
normal fences or fence_arrays. That way we can remove some potential
duplication when using fence_array with sync_file: th
On Fri, 24 Jun 2016, Alex Deucher wrote:
> On Fri, Jun 24, 2016 at 6:15 AM, Frank Binns
> wrote:
>> Signed-off-by: Frank Binns
>
> Reviewed-by: Alex Deucher
Pushed to drm-misc, thanks for the patch and review.
BR,
Jani.
>
>> ---
>> drivers/gpu/drm/drm_irq.c | 4 ++--
>> 1 file changed, 2 i
On Fri, 24 Jun 2016, Chris Wilson wrote:
> This has now been removed from all drivers as it is performed centrally
> as a part of device registration for modesetting drivers. With the last
> user gone, we can unexport it from the DRM module.
>
> Signed-off-by: Chris Wilson
> Cc: David Airlie
> C
Signed-off-by: Nicolas Boichat
---
.../devicetree/bindings/drm/bridge/gpio-mux.txt| 59 ++
1 file changed, 59 insertions(+)
create mode 100644 Documentation/devicetree/bindings/drm/bridge/gpio-mux.txt
diff --git a/Documentation/devicetree/bindings/drm/bridge/gpio-mux.txt
This driver supports single input, 2 output display mux (e.g.
HDMI mux), that provides its status via a GPIO.
Signed-off-by: Nicolas Boichat
---
drivers/gpu/drm/bridge/Kconfig| 11 +
drivers/gpu/drm/bridge/Makefile | 1 +
drivers/gpu/drm/bridge/generic-gpio-mux.c | 347 +
Signed-off-by: Nicolas Boichat
Change-Id: I618ddf114bb93700daf6572d954191e10b6961c8
---
.../devicetree/bindings/drm/bridge/anx7688.txt | 32 ++
1 file changed, 32 insertions(+)
create mode 100644 Documentation/devicetree/bindings/drm/bridge/anx7688.txt
diff --git a/Docu
ANX7688 is a HDMI to DP converter (as well as USB-C port controller),
that has an internal microcontroller.
The only reason a Linux kernel driver is necessary is to reject
resolutions that require more bandwidth than what is available on
the DP side. DP bandwidth and lane count are reported by the
Hi all,
This is a follow up to the 2 patches to add support for ANX7688 sent here:
https://patchwork.kernel.org/patch/9187809/, thanks Archit and Philipp for
the comments.
I also added 2 patches to add support for a simple display MUX, as I'm facing
similar issues while trying to implement it, i.
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/20160627/11a43668/attachment-0001.html>
On Fri, Jun 24, 2016 at 10:13:25AM +0800, Shunqian Zheng wrote:
> drivers/gpu/drm/rockchip/rockchip_drm_drv.c | 100 +++--
> drivers/gpu/drm/rockchip/rockchip_drm_drv.h | 3 +
> drivers/gpu/drm/rockchip/rockchip_drm_gem.c | 221
> ++--
> drivers/gpu/drm/rockchip/
From: Randy Dunlap
Fix build errors when ACPI is not enabled by adding function stubs:
../drivers/gpu/drm/i915/i915_drv.c: In function 'i915_drm_suspend':
../drivers/gpu/drm/i915/i915_drv.c:635:2: error: implicit declaration of
function 'intel_opregion_unregister' [-Werror=implicit-function-dec
t; + if (error) {
> > + dev_err(&client->dev, "Failed to register interrupt\n");
> > + goto err_free_mem;
> > + }
> > +
> > + error = input_register_device(data->input_dev);
> > + if (error)
> > + goto err_free_irq;
> > +
> > + i2c_set_clientdata(client, data);
> > + return 0;
> > +
> > +err_free_irq:
> > + free_irq(client->irq, data);
> > +err_free_mem:
> > + input_free_device(input_dev);
> > + kfree(data);
> > + return error;
> > +}
> > +
> > +static int crtouch_ts_remove(struct i2c_client *client)
> > +{
> > + struct crtouch_ts_data *data = i2c_get_clientdata(client);
> > +
> > + free_irq(client->irq, data);
> > + input_unregister_device(data->input_dev);
> > + kfree(data);
>
> With devm it can all be dropped.
>
> > +
> > + return 0;
> > +}
> > +
> > +static const struct i2c_device_id crtouch_ts_id[] = {
> > + {"crtouch_ts", 0},
> > + { }
> > +};
> > +MODULE_DEVICE_TABLE(i2c, crtouch_ts_id);
> > +
> > +static const struct of_device_id crtouch_ts_dt_ids[] = {
> > + { .compatible = "fsl,crtouch_ts", },
> > + { /* sentinel */ }
> > +};
> > +MODULE_DEVICE_TABLE(of, crtouch_ts_dt_ids);
> > +
> > +static struct i2c_driver crtouch_ts_i2c_driver = {
> > + .driver = {
> > +.name = "crtouch_ts",
> > +.owner = THIS_MODULE,
>
> No need to set owner.
>
> > +.of_match_table = crtouch_ts_dt_ids,
>
> .of_match_table = of_match_ptr(crtouch_ts_dt_ids),
>
> Also, no PM methods?
>
>
Well, the main reason for no PM methods is the original driver did not have
PM methods. I can implement sleep/resume methods, and if all is working
well will submit as part of V2.
> > +},
> > + .probe = crtouch_ts_probe,
> > + .remove = crtouch_ts_remove,
> > + .id_table = crtouch_ts_id,
> > +};
> > +
> > +module_i2c_driver(crtouch_ts_i2c_driver);
> > +
> > +MODULE_AUTHOR("Alison Wang ");
> > +MODULE_DESCRIPTION("Touchscreen driver for Freescale CRTOUCH");
> > +MODULE_LICENSE("GPL");
> > --
> > 2.7.4
> >
>
> Thanks.
>
> --
> Dmitry
>
--
Tony Felice
Support Engineering Manager
Timesys Corporation
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160627/5a5e6817/attachment-0001.html>
On 2016-06-23 17:59, Jon Hunter wrote:
> The I2C driver core for boards using device-tree assumes any subnode of
> an I2C adapter in the device-tree blob as being a I2C slave device.
> Although this makes complete sense, some I2C adapters may have subnodes
> which are not I2C slaves but subnodes pr
On Fri, Jun 10, 2016 at 4:27 PM, Daniel Vetter wrote:
> On Thu, Jun 09, 2016 at 03:32:55PM +0200, Andrea Merello wrote:
>> This driver supports the VGA/LCD core available from OpenCores:
>> http://opencores.org/project,vga_lcd
>>
>> It's intended as a replacement for the "ocfb" framebuffer driver
b6c91 on polaris-test (from
git://people.freedesktop.org/~agd5f/linux)
--
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/20160627/431a13f3/attachment.html>
https://bugzilla.kernel.org/show_bug.cgi?id=119831
--- Comment #10 from Jani Nikula ---
[ 14.841410] nouveau :01:00.0: DRM: evicting buffers...
[ 14.841411] nouveau :01:00.0: DRM: waiting for kernel channels to go
idle...
[ 14.841425] nouveau :01:00.0: DRM: suspending client obj
On Fri, Jun 10, 2016 at 7:36 PM, Rob Herring wrote:
> On Thu, Jun 09, 2016 at 03:33:19PM +0200, Andrea Merello wrote:
>> Signed-off-by: Andrea Merello
>> Cc: Stefan Kristiansson
>> Cc: Tomi Valkeinen
>> Cc: Francesco Diotalevi
>> Cc: Claudio Lorini
>> ---
>> .../bindings/display/opencores,oc
2
> > + VF610_PAD_PTE26__DCU0_B50x42
> > + VF610_PAD_PTE27__DCU0_B60x42
> > + VF610_PAD_PTE28__DCU0_B70x42
> > + >;
> > + };
> > +
> > pinctrl_adc0_ad5: adc0ad5grp {
> > fsl,pins = <
> > VF610_PAD_PTC30__ADC0_SE5
> 0xa1
> > @@ -370,6 +414,10 @@
> > status = "okay";
> > };
> >
> > +&tcon0 {
> > + status = "okay";
> > +};
> > +
> > &uart1 {
> > pinctrl-names = "default";
> > pinctrl-0 = <&pinctrl_uart1>;
>
--
Tony Felice
Support Engineering Manager
Timesys Corporation
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160627/85c17d71/attachment-0001.html>
On 25.06.2016 04:51, Christian König wrote:
> From: Christian König
Typo in the subject: Choose "sanitize" or "sanitise", depending on your
preference. :)
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and
On 06/23/2016 09:28 AM, Daniel Vetter wrote:
> On Thu, Jun 23, 2016 at 8:17 AM, Mario Kleiner
> wrote:
>> The following patch implements precise vblank timestamping
>> for RaspberryPi's VC4, at least for standard progressive
>> scan display modes.
>>
>> It has been tested on the HDMI output with h
MDSS and MDP5 have been separated out in the kernel driver. We no
longer need to keep a track of the start of MDP addesses within
MDSS.
Also, clean up the MDP5 register name prefix. Change it from
"REG_MDP5_MDP_" to "REG_MDP5_".
Signed-off-by: Archit Taneja
---
Used by the "Enable DT Support" ke
On 06/24/2016 09:27 AM, Bibby Hsieh wrote:
> Hi Dave,
>
> Please consider merging this tag, which contains the v2 MT8173 gamma & dither
> function patches I sent on 2016-06-17, rebased onto v4.7-rc1. There have been
> no further comments.
>
> Thanks
> Bibby
>
> The following changes since commi
On Mon, Jun 27, 2016 at 5:37 AM, Frank Binns wrote:
> On 24/06/16 23:08, Alex Deucher wrote:
>>
>> On Fri, Jun 24, 2016 at 1:15 PM, Frank Binns
>> wrote:
>>>
>>> This flag was being set unconditionally at runtime so just set it at
>>> compile time instead.
>>>
>>> Signed-off-by: Frank Binns
>>
>
On 06/27/2016 11:22 AM, Arnd Bergmann wrote:
> ARM SMCCC is only set for ARMv7 and ARMv8 CPUs, but we currently
> allow the driver to be build for older architecture levels as
> well, which results in a link failure:
>
> drivers/gpu/built-in.o: In function `mtk_hdmi_hw_make_reg_writable':
> :(.te
ARM SMCCC is only set for ARMv7 and ARMv8 CPUs, but we currently
allow the driver to be build for older architecture levels as
well, which results in a link failure:
drivers/gpu/built-in.o: In function `mtk_hdmi_hw_make_reg_writable':
:(.text+0x1e737c): undefined reference to `arm_smccc_smc'
This
Hello there,
linux-4.7-rc5/drivers/gpu/drm/amd/powerplay/hwmgr/polaris10_hwmgr.c:1812]:
(style) Variable 'stretch_amount2' is assigned a value that is never
used.
Source code is
else if (stretch_amount == 3 || stretch_amount == 4)
stretch_amount2 = 1;
Suggest either use the variable
This patch looks good to me:
Reviewed-by: Sinclair Yeh
On Thu, Jun 09, 2016 at 02:32:18AM +0300, Laurent Pinchart wrote:
> The driver is the last users of the drm_fb_get_bpp_depth() function. It
> should ideally be converted to use struct drm_mode_fb_cmd2 instead of
> the legacy struct drm_mode_
On 24/06/16 23:08, Alex Deucher wrote:
> On Fri, Jun 24, 2016 at 1:15 PM, Frank Binns
> wrote:
>> This flag was being set unconditionally at runtime so just set it at
>> compile time instead.
>>
>> Signed-off-by: Frank Binns
> Reviewed-by: Alex Deucher
>
> Do you want to take this as part of th
On Mon, Jun 27, 2016 at 6:21 AM, Andrea Merello
wrote:
> On Fri, Jun 10, 2016 at 7:36 PM, Rob Herring wrote:
>> On Thu, Jun 09, 2016 at 03:33:19PM +0200, Andrea Merello wrote:
>>> Signed-off-by: Andrea Merello
>>> Cc: Stefan Kristiansson
>>> Cc: Tomi Valkeinen
>>> Cc: Francesco Diotalevi
>>>
https://bugzilla.kernel.org/show_bug.cgi?id=119831
Zhang Rui changed:
What|Removed |Added
Component|Other |Video(DRI - non Intel)
Assignee|ru
https://bugzilla.kernel.org/show_bug.cgi?id=121021
zhiquan.lee at gmail.com changed:
What|Removed |Added
Component|Video(DRI - non Intel) |Video(Other)
Hardwar
https://bugzilla.kernel.org/show_bug.cgi?id=121021
--- Comment #3 from zhiquan.lee at gmail.com ---
I've added debug kernel command line parameters: drm.debug=0xf when captured
the log.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=121021
--- Comment #2 from zhiquan.lee at gmail.com ---
Created attachment 221261
--> https://bugzilla.kernel.org/attachment.cgi?id=221261&action=edit
kernel 3.14.48 boot up log
--
You are receiving this mail because:
You are watching the assignee of
https://bugzilla.kernel.org/show_bug.cgi?id=121021
--- Comment #1 from zhiquan.lee at gmail.com ---
Created attachment 221251
--> https://bugzilla.kernel.org/attachment.cgi?id=221251&action=edit
kernel 4.6.2 boot up log
--
You are receiving this mail because:
You are watching the assignee of t
https://bugzilla.kernel.org/show_bug.cgi?id=121021
Bug ID: 121021
Summary: drm/i915: kernel suspend during booting up
Product: Drivers
Version: 2.5
Kernel Version: 4.7-rc3, 4.6.2, 3.14.48,
Hardware: Intel
OS: Linux
43 matches
Mail list logo