Re: [Nouveau] [PATCH 000/102] Convert drivers to explicit reset API

Hello, On Thu, 20 Jul 2017 11:36:55 +0200, Philipp Zabel wrote: > > I don't know if it has been discussed in the past, so forgive me if it > > has been. Have you considered adding a "int flags" argument to the > > existing reset_control_get_*() functions, rather than introducing > > separate

[Nouveau] [Bug 94990] [GM204] GTX 970 + 4GB VRAM fails at secboot (v4.6+)

https://bugs.freedesktop.org/show_bug.cgi?id=94990 Ilia Mirkin changed: What|Removed |Added Resolution|--- |FIXED

Re: [Nouveau] [PATCH 000/102] Convert drivers to explicit reset API

On Thu, Jul 20, 2017 at 5:55 AM, Philipp Zabel wrote: > Hi Thomas, > > On Thu, 2017-07-20 at 12:36 +0200, Thomas Petazzoni wrote: >> Hello, >> >> On Thu, 20 Jul 2017 11:36:55 +0200, Philipp Zabel wrote: >> >> > > I don't know if it has been discussed in the past, so

[Nouveau] [PATCH 020/102] drm/nouveau/tegra: explicitly request exclusive reset control

Commit a53e35db70d1 ("reset: Ensure drivers are explicit when requesting reset lines") started to transition the reset control request API calls to explicitly state whether the driver needs exclusive or shared reset control behavior. Convert all drivers requesting exclusive resets to the explicit

[Nouveau] Nouveau driver for NVIDIA Quadro M620?

Dear Nouveau developers, I have a Dell precision M3520 laptop and I have installed fedora 26 but the nouveau driver does not seem to recognise my graphic card NVIDIA Quadro M620. Indeed I can't see it in the llist of the supported card. Do you have any idea whether it will become available and

Re: [Nouveau] [PATCH 000/102] Convert drivers to explicit reset API

Hi Greg, The patches in this series are completely independent of each other, and I would like the subsystem maintainers to apply them at their own leisure. Well, except for the last one, which I will apply only after there are no more users of the transition helpers. On Thu, 2017-07-20 at 10:11

Re: [Nouveau] [PATCH 000/102] Convert drivers to explicit reset API

Hi Thomas, On Thu, 2017-07-20 at 12:36 +0200, Thomas Petazzoni wrote: > Hello, > > On Thu, 20 Jul 2017 11:36:55 +0200, Philipp Zabel wrote: > > > > I don't know if it has been discussed in the past, so forgive me if it > > > has been. Have you considered adding a "int flags" argument to the > >

Re: [Nouveau] [PATCH 000/102] Convert drivers to explicit reset API

On Wed, Jul 19, 2017 at 05:25:04PM +0200, Philipp Zabel wrote: > The reset control API has two modes: exclusive access, where the driver > expects to have full and immediate control over the state of the reset > line, and shared (clock-like) access, where drivers only request reset > deassertion

Re: [Nouveau] [PATCH 000/102] Convert drivers to explicit reset API

On Wed, Jul 19, 2017 at 05:25:04PM +0200, Philipp Zabel wrote: > The reset control API has two modes: exclusive access, where the driver > expects to have full and immediate control over the state of the reset > line, and shared (clock-like) access, where drivers only request reset > deassertion

Re: [Nouveau] [PATCH 000/102] Convert drivers to explicit reset API

Hi, > crypto: rockchip: explicitly request exclusive reset control > iio: adc: rockchip_saradc: explicitly request exclusive reset control > PCI: rockchip: explicitly request exclusive reset control > phy: rockchip-pcie: explicitly request exclusive reset control > phy: rockchip-typec:

[Nouveau] [PATCH 000/102] Convert drivers to explicit reset API

The reset control API has two modes: exclusive access, where the driver expects to have full and immediate control over the state of the reset line, and shared (clock-like) access, where drivers only request reset deassertion while active, but don't care about the state of the reset line while

Re: [Nouveau] [PATCH 000/102] Convert drivers to explicit reset API

Hello, On Wed, 19 Jul 2017 17:25:04 +0200, Philipp Zabel wrote: > The reset control API has two modes: exclusive access, where the driver > expects to have full and immediate control over the state of the reset > line, and shared (clock-like) access, where drivers only request reset > deassertion

Re: [Nouveau] Nouveau driver for NVIDIA Quadro M620?

On 18 July 2017 at 11:42, Patrick Guio wrote: > > Dear Nouveau developers, > > I have a Dell precision M3520 laptop and I have installed fedora 26 but > the nouveau driver does not seem to recognise my graphic card NVIDIA > Quadro M620. Indeed I can't see it in the llist of the

Re: [Nouveau] [RFC PATCH 13/13] clk: thermal throttling

On 2017-07-21 — 23:55, Karol Herbst wrote: > Signed-off-by: Karol Herbst > --- > drm/nouveau/include/nvkm/subdev/clk.h | 1 + > drm/nouveau/nvkm/subdev/clk/base.c| 35 > +++ > 2 files changed, 32 insertions(+), 4 deletions(-) > > diff

[Nouveau] [Bug 94990] [GM204] GTX 970 + 4GB VRAM fails at secboot (v4.6+)

https://bugs.freedesktop.org/show_bug.cgi?id=94990 --- Comment #128 from fariou...@yahoo.fr --- Created attachment 132828 --> https://bugs.freedesktop.org/attachment.cgi?id=132828=edit Xorg.log file KO for fariouche -- You are receiving this mail because: You are the assignee for the

[Nouveau] [Bug 94990] [GM204] GTX 970 + 4GB VRAM fails at secboot (v4.6+)

https://bugs.freedesktop.org/show_bug.cgi?id=94990 --- Comment #129 from fariou...@yahoo.fr --- Created attachment 132829 --> https://bugs.freedesktop.org/attachment.cgi?id=132829=edit kernel log from fariouche when starting X11 -- You are receiving this mail because: You are the assignee for

Re: [Nouveau] [PATCH] drm/nouveau/hwmon: Uninitialized variables in sysfs

Reviewed-by: Pierre Moreau On 2017-07-17 — 11:17, Dan Carpenter wrote: > kstrtol() and friends can return -EINVAL or -ERANGE. We have to test > for both, otherwise the value is possibly uninitialized. Also in some > of these files we accidentally return "count" on error

[Nouveau] [Bug 94990] [GM204] GTX 970 + 4GB VRAM fails at secboot (v4.6+)

https://bugs.freedesktop.org/show_bug.cgi?id=94990 --- Comment #127 from fariou...@yahoo.fr --- Hi, I finally tried the 4.12.2 kernel, and in my case it does not fully work :( I can see a working console, but: - only on my first monitor (DVI) - no x11 (I can see a brief display of xfce4 but