hment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160903/f78793be/attachment.html>
u 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/20160903/e710fedd/attachment-0001.html>
Am 03.09.2016 um 08:01 schrieb Baoyou Xie:
> We get a few warnings when building kernel with W=1:
> drivers/gpu/drm/amd/amdgpu/amdgpu_pll.c:113:6: warning: no previous prototype
> for 'amdgpu_pll_compute' [-Wmissing-prototypes]
> drivers/gpu/drm/amd/amdgpu/cz_smc.c:38:10: warning: no previous prot
Am 03.09.2016 um 07:57 schrieb Baoyou Xie:
> We get a few warnings when building kernel with W=1:
> drivers/gpu/drm/amd/amdgpu/cz_smc.c:51:5: warning: no previous prototype for
> 'cz_send_msg_to_smc_async' [-Wmissing-prototypes]
> drivers/gpu/drm/amd/amdgpu/cz_smc.c:143:5: warning: no previous pro
On Sat, Sep 03, 2016 at 01:57:14PM +0800, Baoyou Xie wrote:
> We get a few warnings when building kernel with W=1:
> drivers/gpu/drm/amd/amdgpu/cz_smc.c:51:5: warning: no previous prototype for
> 'cz_send_msg_to_smc_async' [-Wmissing-prototypes]
> drivers/gpu/drm/amd/amdgpu/cz_smc.c:143:5: warning
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: not available
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160903/40a6d8b2/attachment.sig>
--
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160903/bd639d26/attachment.html>
tps://lists.freedesktop.org/archives/dri-devel/attachments/20160903/b57187eb/attachment.html>
Hey
On Sat, Sep 3, 2016 at 2:01 PM, Noralf Trønnes wrote:
>
> Den 02.09.2016 10:22, skrev David Herrmann:
>>
>> The SimpleDRM driver binds to simple-framebuffer devices and provides a
>> DRM/KMS API. It provides only a single CRTC+encoder+connector combination
>> plus one initial mode.
>>
>> Use
Den 02.09.2016 10:22, skrev David Herrmann:
> There are several situations where we want hardware handover from an early
> boot GFX driver (e.g., vgacon, vesafb, efifb, simplefb) to a full fletched
> GFX driver (e.g., most DRM drivers). So far, we relied on
> remove_conflicting_framebuffers() to d
Den 02.09.2016 10:22, skrev David Herrmann:
> The SimpleDRM driver binds to simple-framebuffer devices and provides a
> DRM/KMS API. It provides only a single CRTC+encoder+connector combination
> plus one initial mode.
>
> Userspace can create dumb-buffers which can be blit into the real
> framebu
Den 02.09.2016 10:22, skrev David Herrmann:
> Create a simple fbdev device during SimpleDRM setup so legacy user-space
> and fbcon can use it.
>
> Signed-off-by: David Herrmann
[...]
> diff --git a/drivers/gpu/drm/simpledrm/simpledrm_fbdev.c
> b/drivers/gpu/drm/simpledrm/simpledrm_fbdev.c
[..
.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160903/7410f95f/attachment.html>
Den 02.09.2016 10:22, skrev David Herrmann:
> Switch over all DRM drivers to use the new sysfb_evict_conflicts()
> infrastructure. The only non-trivial conversion is i915, since it does not
> make use of the generic PCI resources, but assembles the apertures via
> intel ggtt queries.
>
> Signed-of
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160903/3f740be8/attachment-0001.html>
drmFreeDevice` say?
--
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/20160903/540f13c5/attachment.html>
Den 03.09.2016 14:04, skrev Noralf Trønnes:
>
> Den 02.09.2016 10:22, skrev David Herrmann:
>> Create a simple fbdev device during SimpleDRM setup so legacy user-space
>> and fbcon can use it.
>>
>> Signed-off-by: David Herrmann
>
> [...]
>
>> diff --git a/drivers/gpu/drm/simpledrm/simpledrm_fbd
t;Blender".
--
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/20160903/2ebaf105/attachment.html>
next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160903/cffb8be8/attachment.html>
dri-devel/attachments/20160903/9646daa4/attachment.html>
rmware from
Catalyst?
@Marek, where is the best place to report this?
--
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/20160903/0
older version of mesa
against it, the problem still occurs.
--
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/20160903
for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160903/b89587ed/attachment.html>
for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160903/b0e1a4b6/attachment.html>
ceiving 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/20160903/02112875/attachment.html>
This patch adds the documentation for rockchip dfi devfreq-event driver.
Signed-off-by: Lin Huang
---
Changes in v8:
- delete a unuse blank line
Changes in v7:
- None
Changes in v6:
- None
Changes in v5:
- None
Changes in v4:
- None
Changes in v3:
- None
Changes in v2:
- None
Changes in v
base on dfi result, we do ddr frequency scaling, register
dmc driver to devfreq framework, and use simple-ondemand
policy.
Signed-off-by: Lin Huang
Signed-off-by: MyngJoo Ham
Reviewed-by: Chanwoo Choi
---
Changes in v8:
- None
Changes in v8:
- do not use ddr_timing node, get ddr timing directl
TL);
> >
> > @@ -145,7 +145,7 @@ static int
> iceland_program_jump_on_start(struct amdgpu_device *adev)
> > return 0;
> > }
> >
> > -void iceland_stop_smc_clock(struct amdgpu_device *adev)
> > +static void iceland_stop_smc_clock(struct amdgpu_device *adev)
> > {
> > uint32_t val = RREG32_SMC(ixSMC_SYSCON_CLOCK_CNTL_0);
> >
> > @@ -153,7 +153,7 @@ void iceland_stop_smc_clock(struct
> amdgpu_device *adev)
> > WREG32_SMC(ixSMC_SYSCON_CLOCK_CNTL_0, val);
> > }
> >
> > -void iceland_start_smc_clock(struct amdgpu_device *adev)
> > +static void iceland_start_smc_clock(struct amdgpu_device *adev)
> > {
> > uint32_t val = RREG32_SMC(ixSMC_SYSCON_CLOCK_CNTL_0);
> >
> >
>
>
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160903/b476f729/attachment-0001.sig>
rk3399 platform have dfi controller can monitor ddr load,
and dcf controller to handle ddr register so we can get the
right ddr frequency and make ddr controller happy work(which
will implement in bl31). So we do ddr frequency scaling with
following flow:
kernel
rk3399 platform have dfi controller can monitor ddr load,
and dcf controller to handle ddr register so we can get the
right ddr frequency and make ddr controller happy work(which
will implement in bl31). So we do ddr frequency scaling with
following flow:
kernel
This patch adds the documentation for rockchip dfi devfreq-event driver.
Signed-off-by: Lin Huang
---
Changes in v9:
- reorder compatible and reg
Changes in v8:
- delete a unuse blank line
Changes in v7:
- None
Changes in v6:
- None
Changes in v5:
- None
Changes in v4:
- None
Changes in v3:
on rk3399 platform, there is dfi conroller can monitor
ddr load, base on this result, we can do ddr freqency
scaling.
Signed-off-by: Lin Huang
Signed-off-by: MyungJoo Ham
Acked-by: Chanwoo Choi
---
Changes in v9:
-None
Changes in v8:
-None
Changes in v7:
-access need to *4 to get right DDR lo
when in ddr frequency scaling process, vop can not do enable or
disable operation, since in dcf we check vop clock to see whether
vop work. If vop work, dcf do ddr frequency scaling when vop
in vblank status, and we need to read vop register to check whether
vop go into vblank status. If vop not wo
We get a few warnings when building kernel with W=1:
drivers/gpu/drm/amd/amdgpu/cz_smc.c:51:5: warning: no previous prototype for
'cz_send_msg_to_smc_async' [-Wmissing-prototypes]
drivers/gpu/drm/amd/amdgpu/cz_smc.c:143:5: warning: no previous prototype for
'cz_write_smc_sram_dword' [-Wmissing-pr
We get a few warnings when building kernel with W=1:
drivers/gpu/drm/amd/amdgpu/amdgpu_pll.c:113:6: warning: no previous prototype
for 'amdgpu_pll_compute' [-Wmissing-prototypes]
drivers/gpu/drm/amd/amdgpu/cz_smc.c:38:10: warning: no previous prototype for
'cz_get_argument' [-Wmissing-prototypes]
amdgpu_device *adev)
> {
> uint32_t val = RREG32_SMC(ixSMC_SYSCON_CLOCK_CNTL_0);
>
> @@ -153,7 +153,7 @@ void iceland_stop_smc_clock(struct amdgpu_device *adev)
> WREG32_SMC(ixSMC_SYSCON_CLOCK_CNTL_0, val);
> }
>
> -void iceland_start_smc_clock(struct amdgpu_device *adev)
> +static void iceland_start_smc_clock(struct amdgpu_device *adev)
> {
> uint32_t val = RREG32_SMC(ixSMC_SYSCON_CLOCK_CNTL_0);
>
>
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160903/4d82b78e/attachment-0001.sig>
t; }
> >
> > -void iceland_reset_smc(struct amdgpu_device *adev)
> > +static void iceland_reset_smc(struct amdgpu_device *adev)
> > {
> > uint32_t val = RREG32_SMC(ixSMC_SYSCON_RESET_CNTL);
> >
> > @@ -145,7 +145,7 @@ static int iceland_program_jump_on_start(struct
> amdgpu_device *adev)
> > return 0;
> > }
> >
> > -void iceland_stop_smc_clock(struct amdgpu_device *adev)
> > +static void iceland_stop_smc_clock(struct amdgpu_device *adev)
> > {
> > uint32_t val = RREG32_SMC(ixSMC_SYSCON_CLOCK_CNTL_0);
> >
> > @@ -153,7 +153,7 @@ void iceland_stop_smc_clock(struct amdgpu_device
> *adev)
> > WREG32_SMC(ixSMC_SYSCON_CLOCK_CNTL_0, val);
> > }
> >
> > -void iceland_start_smc_clock(struct amdgpu_device *adev)
> > +static void iceland_start_smc_clock(struct amdgpu_device *adev)
> > {
> > uint32_t val = RREG32_SMC(ixSMC_SYSCON_CLOCK_CNTL_0);
> >
> >
>
>
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160903/322c5fb4/attachment-0001.html>
>
> > @@ -129,7 +129,7 @@ void iceland_start_smc(struct amdgpu_device *adev)
> > WREG32_SMC(ixSMC_SYSCON_RESET_CNTL, val);
> > }
> >
> > -void iceland_reset_smc(struct amdgpu_device *adev)
> > +static void iceland_reset_smc(struct amdgpu_device *adev)
> > {
> > uint32_t val = RREG32_SMC(ixSMC_SYSCON_RESET_CNTL);
> >
> > @@ -145,7 +145,7 @@ static int iceland_program_jump_on_start(struct
> amdgpu_device *adev)
> > return 0;
> > }
> >
> > -void iceland_stop_smc_clock(struct amdgpu_device *adev)
> > +static void iceland_stop_smc_clock(struct amdgpu_device *adev)
> > {
> > uint32_t val = RREG32_SMC(ixSMC_SYSCON_CLOCK_CNTL_0);
> >
> > @@ -153,7 +153,7 @@ void iceland_stop_smc_clock(struct amdgpu_device
> *adev)
> > WREG32_SMC(ixSMC_SYSCON_CLOCK_CNTL_0, val);
> > }
> >
> > -void iceland_start_smc_clock(struct amdgpu_device *adev)
> > +static void iceland_start_smc_clock(struct amdgpu_device *adev)
> > {
> > uint32_t val = RREG32_SMC(ixSMC_SYSCON_CLOCK_CNTL_0);
> >
> >
>
>
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160903/74ebce5c/attachment-0001.html>
Calling 'list_splice_tail' followed by 'INIT_LIST_HEAD' is equivalent to
'list_splice_tail_init'.
This has been spotted with the following coccinelle script:
/
@@
expression y,z;
@@
- list_splice_tail(y,z);
- INIT_LIST_HEAD(y);
+ list_splice_tail_init(y,z);
Signed-off-by: Christophe JA
This patch adds the documentation for rockchip rk3399 dmc driver.
Signed-off-by: Lin Huang
---
Changes in v9:
- add ddr timing property to node
Changes in v8:
- add ddr timing properties
Changes in v7:
- None
Changes in v6:
-Add more detail in Documentation
Changes in v5:
-None
Changes in v4
On Sat, Sep 3, 2016 at 3:06 AM, Maxime Ripard
wrote:
> Hi Icenowy,
>
> On Fri, Sep 02, 2016 at 09:30:05AM +0800, Icenowy Zheng wrote:
>>
>>
>> 01.09.2016, 23:40, "Maxime Ripard" :
>> > Hi everyone,
>> >
>> > This serie introduces the support in the sun4i-drm driver for the A33.
>> >
>> > Beside th
41 matches
Mail list logo