On 23 January 2015 at 18:05, Thierry Reding wrote:
> From: Thierry Reding
>
> The current implementation is limited by the number of addresses that
> fit into an unsigned long. This causes problems on 32-bit Tegra where
> unsigned long is 32-bit but drm_mm is used to manage an IOVA space of
> 4 G
On 23 January 2015 at 23:56, Thierry Reding wrote:
> Hi Dave,
>
> The following changes since commit 281d1bbd34b734e4f22b30b6f3b673dda46a7470:
>
> Merge remote-tracking branch 'origin/master' into drm-next (2015-01-22
> 10:44:41 +1000)
>
> are available in the git repository at:
>
> git://ano
On 26 January 2015 at 23:12, Heiko Stübner wrote:
> Commits 8eb17f05bc18 ("drm/bridge: do not pass drm_bridge_funcs to
> drm_bridge_init") and fbc4572e9c48 ("drm/bridge: make bridge registration
> independent of drm flow") changed the bridge API without taking into account
> the also newly introd
From: Dave Airlie
So sti doesn't build because the bridge interfaces changes didn't
catch up to its new DVO driver.
Now I might just carry this patch, but I might just push the
bridge pull into a side-pull until someone resolves it.
So this might not be the right solution to the problem, so
ple
Dear Emil,
On Mon, 26 Jan 2015 19:05:51 +
Emil Velikov wrote:
> On 26 January 2015 at 01:42, Hyungwon Hwang
> wrote:
> > Dear Tobias,
> >
> > Thanks for fixing it.
> >
> > Signed-off-by: Hyungwon Hwang
> >
> Hi Hyungwon Hwang
>
> I'm a bit confused about the use of s-o-b here. I've assume
From: Donghwa Lee
This patch adds MIPI-DSI based S6E3HA2 panel driver. This panel has
1440x2560 resolution in 5.7-inch physical panel.
Signed-off-by: Donghwa Lee
Signed-off-by: Hyungwon Hwang
Cc: Inki Dae
Cc: Sangbae Lee
---
Changes for v2:
- Fix errata in documentation and source code comme
Hi Linus,
This feels larger than I'd like but its for three reasons.
a) amdkfd finalising the API more, this is a new feature introduced last
merge window, and I'd prefer to make the tweaks
to the API before it first gets into a stable release.
b) radeon regression required splitting an intern
c6, the gpu locked up after a few seconds of playing the
same video.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/2015012
On 27 January 2015 at 01:05, Hyungwon Hwang wrote:
> Dear Emil,
>
> On Mon, 26 Jan 2015 19:05:51 +
> Emil Velikov wrote:
>
>> On 26 January 2015 at 01:42, Hyungwon Hwang
>> wrote:
>> > Dear Tobias,
>> >
>> > Thanks for fixing it.
>> >
>> > Signed-off-by: Hyungwon Hwang
>> >
>> Hi Hyungwon H
On 27.01.2015 04:20, Dieter Nützel wrote:
> make[1]: Leaving directory '/opt/llvm/bindings'
> llvm[0]: * Completed Debug+Asserts Build
> llvm[0]: * Note: Debug build can be 10 times slower than an
> llvm[0]: * optimized build. Use make ENABLE_OPTIMIZED=1 to
> llvm[0]: * make an opt
HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150127/bbe87c3d/attachment.html>
Hi Kukjin,
On Fri, Jan 23, 2015 at 12:31 PM, Kukjin Kim wrote:
> Ajay Kumar wrote:
>>
>> Define videoports and use endpoints to describe the connection between
>> the encoder, bridge and the panel, instead of using phandles.
>>
>> Signed-off-by: Ajay Kumar
>> Acked-by: Inki Dae
>> Tested-by: Ra
y come from
somewhere else (drm)?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150127/732639fd/attachment.html>
On 01/26/2015 11:51 PM, Dave Airlie wrote:
> On 23 January 2015 at 18:05, Thierry Reding
> wrote:
>> From: Thierry Reding
>>
>> The current implementation is limited by the number of addresses that
>> fit into an unsigned long. This causes problems on 32-bit Tegra where
>> unsigned long is 32-bi
L attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150127/d0712502/attachment.html>
Hi Russell!
On 21 January 2015 at 23:01, Russell King - ARM Linux
wrote:
> On Wed, Jan 21, 2015 at 09:46:47AM +0530, Sumit Semwal wrote:
>> +static int calc_constraints(struct device *dev,
>> + struct dma_buf_constraints *calc_cons)
>> +{
>> + struct dma_buf_constraint
On Mon, 26 Jan 2015, Kumar Amit Mehta wrote:
> The comment for intel_cpu_fifo_underrun_irq_handler() is not consistent
> with the code and the rest of the comment for this routine. This patch
> fixes this typo in comment.
>
> Signed-off-by: Kumar Amit Mehta
Reviewed-by: Jani Nikula
> ---
> d
https://bugzilla.kernel.org/show_bug.cgi?id=91861
--- Comment #4 from Mike S. ---
I haven't yet tested the patch to cap ref_div to 7, but here are the values
reported with drm.debug=0xE, in case they are useful:
1. Kernel 3.14 (working):
14851, fb: 145.2 ref: 2, post: 7
2. Kernel 3.18 (not work
t rather that using an unsigned long for a size on a 32-bit machine
will give you 4 GiB - 1 addresses. The IOMMU page size is still 4 KiB
for Tegra.
Thierry
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150127/e6f76b7d/attachment.sig>
From: Rob Clark
For devices which have constraints about maximum number of segments in
an sglist. For example, a device which could only deal with contiguous
buffers would set max_segment_count to 1.
The initial motivation is for devices sharing buffers via dma-buf,
to allow the buffer exporter
Add some helpers to share the constraints of devices while attaching
to the dmabuf buffer.
At each attach, the constraints are calculated based on the following:
- max_segment_size, max_segment_count, segment_boundary_mask from
device_dma_parameters.
In case the attaching device's constraints
On 01/27/2015 09:15 AM, Thierry Reding wrote:
> On Tue, Jan 27, 2015 at 07:07:44AM +0100, Thomas Hellstrom wrote:
>> On 01/26/2015 11:51 PM, Dave Airlie wrote:
>>> On 23 January 2015 at 18:05, Thierry Reding
wrote:
From: Thierry Reding
The current implementation is limited by the n
https://bugzilla.kernel.org/show_bug.cgi?id=91861
Christian König changed:
What|Removed |Added
CC||deathsimple at vodafone.de
--- Comment
On Tue, Jan 27, 2015 at 08:51:12AM +1000, Dave Airlie wrote:
> On 23 January 2015 at 18:05, Thierry Reding
> wrote:
> > From: Thierry Reding
> >
> > The current implementation is limited by the number of addresses that
> > fit into an unsigned long. This causes problems on 32-bit Tegra where
> >
Hi Dave,
The following changes since commit 281d1bbd34b734e4f22b30b6f3b673dda46a7470:
Merge remote-tracking branch 'origin/master' into drm-next (2015-01-22
10:44:41 +1000)
are available in the git repository at:
git://anongit.freedesktop.org/tegra/linux tags/drm/tegra/for-3.20-rc1
for yo
On Tue, Jan 27, 2015 at 09:56:49AM +0200, Jani Nikula wrote:
> On Mon, 26 Jan 2015, Kumar Amit Mehta wrote:
> > The comment for intel_cpu_fifo_underrun_irq_handler() is not consistent
> > with the code and the rest of the comment for this routine. This patch
> > fixes this typo in comment.
> >
> >
dri-devel/attachments/20150127/a98fc5e6/attachment.html>
|--- |FIXED
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150127/c178287a/attachment.html>
i-devel/attachments/20150127/2eab80f1/attachment.html>
Hi Dave,
Mostly just small fixes and polish all over, plus the dpms-on-atomic
stuff.
Cheers, Daniel
The following changes since commit 281d1bbd34b734e4f22b30b6f3b673dda46a7470:
Merge remote-tracking branch 'origin/master' into drm-next (2015-01-22
10:44:41 +1000)
are available in the git r
L attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150127/ceacf669/attachment.html>
The exynos_drm_dmabuf.c file doesn't include any module feature and it
isn't built to module.
Signed-off-by: Joonyoung Shim
---
drivers/gpu/drm/exynos/exynos_drm_dmabuf.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/gpu/drm/exynos/exynos_drm_dmabuf.c
b/drivers/gpu/drm/exynos/e
The exynos drm driver has DRIVER_PRIME capability, then it's reasonable
to support dmabuf as default. Remove DRM_EXYNOS_DMABUF config, it will
prevent that user selects the option unnecessarily.
Signed-off-by: Joonyoung Shim
---
This patch can be conflicted below link patch of Marek to remove
sel
Hi,
On 23 January 2015 at 12:42, Gustavo Padovan wrote:
> void exynos_drm_crtc_finish_pageflip(struct drm_device *dev, int pipe)
> {
> struct exynos_drm_private *dev_priv = dev->dev_private;
> - struct drm_pending_vblank_event *e, *t;
> struct drm_crtc *drm_crtc = dev_priv
2015-01-27 Joonyoung Shim :
> The exynos drm driver has DRIVER_PRIME capability, then it's reasonable
> to support dmabuf as default. Remove DRM_EXYNOS_DMABUF config, it will
> prevent that user selects the option unnecessarily.
>
> Signed-off-by: Joonyoung Shim
> ---
> This patch can be conflic
2015-01-27 Joonyoung Shim :
> The exynos_drm_dmabuf.c file doesn't include any module feature and it
> isn't built to module.
>
> Signed-off-by: Joonyoung Shim
> ---
> drivers/gpu/drm/exynos/exynos_drm_dmabuf.c | 4
> 1 file changed, 4 deletions(-)
Reviewed-by: Gustavo Padovan
G
On Tue, Jan 27, 2015 at 12:59:15PM +, Daniel Stone wrote:
> Hi,
>
> On 23 January 2015 at 12:42, Gustavo Padovan wrote:
> > void exynos_drm_crtc_finish_pageflip(struct drm_device *dev, int pipe)
> > {
> > struct exynos_drm_private *dev_priv = dev->dev_private;
> > - struct drm
On Mon, Jan 26, 2015 at 04:39:29PM +, Simon Farnsworth wrote:
> On Monday 26 January 2015 18:11:01 Ville Syrjälä wrote:
> > On Mon, Jan 26, 2015 at 03:47:13PM +, Simon Farnsworth wrote:
> > > On Monday 26 January 2015 17:33:35 Ville Syrjälä wrote:
> > > > On Mon, Jan 26, 2015 at 03:22:4
the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150127/b9066305/attachment.html>
the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150127/61fd044c/attachment-0001.html>
Hi Fabio,
Am Dienstag, den 27.01.2015, 10:54 -0200 schrieb Fabio Estevam:
> If devm_request_threaded_irq() fails we should jump to 'err_iahb' label that
> will disable the clocks that were previously enabled.
>
> Signed-off-by: Fabio Estevam
> ---
> drivers/gpu/drm/bridge/dw_hdmi.c | 2 +-
> 1
DisplayPort to DVI-D Dual Link adapters designed by Bizlink have bugs in
their I2C over AUX implementation. They work fine with Windows, but fail
with Linux.
It turns out that they cannot keep an I2C transaction open unless the
previous read was 16 bytes; shorter reads can only be followed by a ze
Compare to Dave's patch this one doesn't take care of driver unbind
but that is a general issue I have to address in STI driver.
I would like to fix all unbind issues (hdmi, dvo, hda) in the same way
but it isn't link to this topic.
so you could my ack on this patch, up to me to fix unbind problem
MDP5 hardware has some limitation and requires to avoid flushing
registers more than once between two Vblanks.
This change removes all FLUSH operations (except for HW cursor)
beside the one coming from a CRTC's ->atomic_flush().
This avoid this type of behavior (eg: CRTC + 1 plane overlay):
On Mon, Jan 26, 2015 at 6:06 PM, Dave Airlie wrote:
>
> are available in the git repository at:
>
> git://people.freedesktop.org/~airlied/linux drm-fixes
No they aren't, actually, because you've screwed up your repository.
It looks like you were using an alternates that has gone away:
remo
--
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150127/3792ad04/attachment.html>
ttachments/20150127/8bc96ff1/attachment.html>
On Tue, Jan 27, 2015 at 09:31:26AM +0100, Thomas Hellstrom wrote:
> On 01/27/2015 09:15 AM, Thierry Reding wrote:
> > Are you referring to the 4 GiB - 1 comment? The point I was trying to
> > make is not that the granularity of the IOVA space needs to be 1 byte
> > but rather that using an unsigned
From: Fabio Estevam
Building for arm64 causes the following warnings:
drivers/gpu/drm/drm_gem_cma_helper.c: In function 'drm_gem_cma_create':
drivers/gpu/drm/drm_gem_cma_helper.c:114:4: warning: format '%d' expects
argument of type 'int', but argument 3 has type 'size_t' [-Wformat=]
size);
Hi All
Please find modifed set of patches using regmap interface to accedd the PMIC
registers. These patches implement a drm_panel as a platform driver for the
mfd_cell device declared in intel_soc_pmic_core.c.
DRM is extended to provide a find panel by name in absence of OF.
Backlight control
This allows for proper PPS during enable/disable of BYT-T platforms
where these signals are routed through PMIC. Needs DRM_PANEL to be
selected by default as well
v2: Adapt to panel find function name change in drm_panel
Signed-off-by: Shobhit Kumar
---
drivers/gpu/drm/i915/Kconfig
For scenarios where OF is not available, we can use panel identification by
name.
Signed-off-by: Shobhit Kumar
---
drivers/gpu/drm/drm_panel.c | 18 ++
include/drm/drm_panel.h | 3 +++
2 files changed, 21 insertions(+)
diff --git a/drivers/gpu/drm/drm_panel.c b/drivers/gpu/
On BYT-T configuration, panel enable/disable signals are routed through
PMIC. Add a cell device for the same.
Signed-off-by: Shobhit Kumar
---
drivers/mfd/intel_soc_pmic_crc.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/mfd/intel_soc_pmic_crc.c b/drivers/mfd/intel_soc_pmic_crc
This driver provides support for the "crystal_cove_panel" cell device.
On BYT-T pmic has to be used to enable/disable panel.
v2: Addressed Jani's comments
- Moved inside i915
- Correct licensing
- Remove unused stuff
- Do not initialize prepare/unprepare as they are not needed as o
Commit fbc4572e9c48e45b ("drm/bridge: make bridge registration independent of
drm flow") introduced some drm/bridge API modifications. Make the necessary
changes so that we can avoid the build breakage:
drivers/gpu/drm/sti/sti_dvo.c: In function 'sti_dvo_brigde_destroy':
drivers/gpu/drm/sti/sti_dv
Commit fbc4572e9c48e45b ("drm/bridge: make bridge registration independent of
drm flow") introduced some drm/bridge API modifications. Make the necessary
changes so that we can avoid the build breakage:
drivers/gpu/drm/bridge/dw_hdmi.c: In function 'dw_hdmi_bridge_destroy':
drivers/gpu/drm/bridge/
If devm_request_threaded_irq() fails we should jump to 'err_iahb' label that
will disable the clocks that were previously enabled.
Signed-off-by: Fabio Estevam
---
drivers/gpu/drm/bridge/dw_hdmi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/bridge/dw_hdmi
57 matches
Mail list logo
