Displaying 20 results from an estimated 200 matches similar to: "[PATCH] clk/gm20b: fix build on non-tegra platforms"
2016 Jun 01
15
[PATCH 00/15] clk/tegra: improve code and add DFS support
This series adds support for GM20B PLL's Maxwell features, namely glitchless
switch and (more importantly) DFS support. DFS lets the PLL lower its output
speed according to input current variations, making the clock more stable and
allowing it to run safely at lower voltage.
All GM20B additions are done in the last patch, which consequently ends up
being considerably big ; fortunately, it
2020 May 29
2
[PATCH] drm/nouveau/clk/gm20b: Fix memory leak in gm20b_clk_new
When gk20a_clk_ctor() returns an error code, pointer "clk"
should be released. It's the same when gm20b_clk_new()
returns from elsewhere following this call.
Signed-off-by: Dinghao Liu <dinghao.liu at zju.edu.cn>
---
drivers/gpu/drm/nouveau/nvkm/subdev/clk/gm20b.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
2020 May 31
0
[PATCH] drm/nouveau/clk/gm20b: Fix memory leak in gm20b_clk_new
On Sat, 30 May 2020 at 19:42, Dinghao Liu <dinghao.liu at zju.edu.cn> wrote:
>
> When gk20a_clk_ctor() returns an error code, pointer "clk"
> should be released. It's the same when gm20b_clk_new()
> returns from elsewhere following this call.
This shouldn't be necessary. If a subdev constructor fails, and
returns a pointer, the core will call the destructor to
2020 Feb 14
0
[PATCH AUTOSEL 5.5 355/542] drm/nouveau/secboot/gm20b: initialize pointer in gm20b_secboot_new()
From: Dan Carpenter <dan.carpenter at oracle.com>
[ Upstream commit 3613a9bea95a1470dd42e4ed1cc7d86ebe0a2dc0 ]
We accidentally set "psb" which is a no-op instead of "*psb" so it
generates a static checker warning. We should probably set it before
the first error return so that it's always initialized.
Fixes: 923f1bd27bf1 ("drm/nouveau/secboot/gm20b: add
2020 Feb 14
0
[PATCH AUTOSEL 5.4 309/459] drm/nouveau/secboot/gm20b: initialize pointer in gm20b_secboot_new()
From: Dan Carpenter <dan.carpenter at oracle.com>
[ Upstream commit 3613a9bea95a1470dd42e4ed1cc7d86ebe0a2dc0 ]
We accidentally set "psb" which is a no-op instead of "*psb" so it
generates a static checker warning. We should probably set it before
the first error return so that it's always initialized.
Fixes: 923f1bd27bf1 ("drm/nouveau/secboot/gm20b: add
2020 Feb 14
0
[PATCH AUTOSEL 4.19 168/252] drm/nouveau/secboot/gm20b: initialize pointer in gm20b_secboot_new()
From: Dan Carpenter <dan.carpenter at oracle.com>
[ Upstream commit 3613a9bea95a1470dd42e4ed1cc7d86ebe0a2dc0 ]
We accidentally set "psb" which is a no-op instead of "*psb" so it
generates a static checker warning. We should probably set it before
the first error return so that it's always initialized.
Fixes: 923f1bd27bf1 ("drm/nouveau/secboot/gm20b: add
2020 Feb 14
0
[PATCH AUTOSEL 4.14 125/186] drm/nouveau/secboot/gm20b: initialize pointer in gm20b_secboot_new()
From: Dan Carpenter <dan.carpenter at oracle.com>
[ Upstream commit 3613a9bea95a1470dd42e4ed1cc7d86ebe0a2dc0 ]
We accidentally set "psb" which is a no-op instead of "*psb" so it
generates a static checker warning. We should probably set it before
the first error return so that it's always initialized.
Fixes: 923f1bd27bf1 ("drm/nouveau/secboot/gm20b: add
2016 Sep 23
1
[PATCH] drm/nouveau/secboot/gm20b: Fix return value in case of error
If 'ioremap()' returns 0, 'gm20b_tegra_read_wpr()' will return 0 as well,
which means success.
Return -ENOMEM instead
Signed-off-by: Christophe JAILLET <christophe.jaillet at wanadoo.fr>
---
Not sure that -ENOMEM is the best value.
I've taken it because it is often used in such a case.
---
drivers/gpu/drm/nouveau/nvkm/subdev/secboot/gm20b.c | 2 +-
1 file changed, 1
[PATCH -next] drm/nouveau/secboot/gm20b: fix the error return code in gm20b_secboot_tegra_read_wpr()
2017 Apr 25
0
[PATCH -next] drm/nouveau/secboot/gm20b: fix the error return code in gm20b_secboot_tegra_read_wpr()
From: Wei Yongjun <weiyongjun1 at huawei.com>
The error return code PTR_ERR(mc) is always 0 since mc is
equal to 0 in this error handling case.
Signed-off-by: Wei Yongjun <weiyongjun1 at huawei.com>
---
drivers/gpu/drm/nouveau/nvkm/subdev/secboot/gm20b.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/secboot/gm20b.c
2020 Jan 15
0
[PATCH] drm/nouveau: gm20b, gp10b: Fix Falcon bootstrapping
From: Thierry Reding <treding at nvidia.com>
The low-level Falcon bootstrapping callbacks are expected to return 0 on
success or a negative error code on failure. However, the implementation
on Tegra returns the ID or mask of the Falcons that were bootstrapped on
success, thus breaking the calling code, which treats this as failure.
Fix this by making sure we only return 0 or a negative
2020 Jan 08
1
[PATCH] nouveau/secboot/gm20b: initialize pointer in gm20b_secboot_new()
We accidentally set "psb" which is a no-op instead of "*psb" so it
generates a static checker warning. We should probably set it before
the first error return so that it's always initialized.
Fixes: 923f1bd27bf1 ("drm/nouveau/secboot/gm20b: add secure boot support")
Signed-off-by: Dan Carpenter <dan.carpenter at oracle.com>
---
Static analysis. I'm
2017 Apr 20
0
[bug report] drm/nouveau/secboot/gm20b: add secure boot support
Hello Alexandre Courbot,
The patch 923f1bd27bf1: "drm/nouveau/secboot/gm20b: add secure boot
support" from Feb 24, 2016, leads to the following static checker
warning:
drivers/gpu/drm/nouveau/nvkm/subdev/secboot/gm20b.c:129 gm20b_secboot_new()
warn: did you mean to set '*psb' instead of 'psb'
drivers/gpu/drm/nouveau/nvkm/subdev/secboot/gm20b.c
103 int
104
2016 Oct 27
0
[PATCH 3/3] fb: add gm20b device
gm20b's FB has the same capabilities as gm200, minus the ability to
allocate RAM. Create a device that reflects this instead of re-using the
gk20a device which may be incorrect.
Signed-off-by: Alexandre Courbot <acourbot at nvidia.com>
---
drm/nouveau/include/nvkm/subdev/fb.h | 1 +
drm/nouveau/nvkm/engine/device/base.c | 2 +-
drm/nouveau/nvkm/subdev/fb/Kbuild | 1 +
2016 Mar 31
1
[PATCH] platform: disable probe of GM20B
On 4.6, probing GM20B will freeze the system because of a missing clock
that Nouveau must also enable. Since the DT bindings for this clock
did not make it in time for 4.6, disable it for now.
Signed-off-by: Alexandre Courbot <acourbot at nvidia.com>
---
Ben, sorry for that, but could you take this for one of the next -rc? I
will re-enable GM20B once the DT bindings have landed. Thanks!
2016 Jul 13
0
Error handling in drivers/gpu/drm/nouveau/nvkm/subdev/secboot/gm20b.c
Hi,
in file 'drivers/gpu/drm/nouveau/nvkm/subdev/secboot/gm20b.c', error
handling in 'gm20b_tegra_read_wpr()' seams to be broken.
The code used is:
mc = ioremap(TEGRA_MC_BASE, 0xd00);
if (!mc) {
nvkm_error(&sb->subdev, "...");
return PTR_ERR(mc);
}
so we always return '0', which means success.
Best regards,
CJ
2023 Jan 15
3
[REGRESSION] GM20B probe fails after commit 2541626cfb79
On Thu, Dec 29, 2022 at 12:58 AM Diogo Ivo <diogo.ivo at tecnico.ulisboa.pt> wrote:
>
> Hello,
>
> Commit 2541626cfb79 breaks GM20B probe with
> the following kernel log:
>
> [ 2.153892] ------------[ cut here ]------------
> [ 2.153897] WARNING: CPU: 1 PID: 36 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273 gf100_vmm_valid+0x2c4/0x390
> [
2024 Nov 12
1
[REGRESSION] GM20B pmu timeout
On Tue, 12 Nov 2024 at 22:34, Linux regression tracking (Thorsten
Leemhuis) <regressions at leemhuis.info> wrote:
>
> [CCing Danilo, who committed the culprit]
>
> On 04.11.24 13:11, Diogo Ivo wrote:
> > On Tue Oct 15, 2024 at 7:13 PM WEST, Linux regression tracking (Thorsten Leemhuis) wrote:
> >> On 10.10.24 15:32, Diogo Ivo wrote:
> >>>
>
2024 Nov 04
1
[REGRESSION] GM20B pmu timeout
Hello,
On Tue Oct 15, 2024 at 7:13 PM WEST, Linux regression tracking (Thorsten Leemhuis) wrote:
> Hi, Thorsten here, the Linux kernel's regression tracker.
>
> On 10.10.24 15:32, Diogo Ivo wrote:
> >
> > Somewhere between 6.11-rc4 and 6.11-rc5 the following error message is displayed
> > when trying to initialize a nvc0_screen on the Tegra X1's GM20B:
>
2024 Nov 12
1
[REGRESSION] GM20B pmu timeout
[CCing Danilo, who committed the culprit]
On 04.11.24 13:11, Diogo Ivo wrote:
> On Tue Oct 15, 2024 at 7:13 PM WEST, Linux regression tracking (Thorsten Leemhuis) wrote:
>> On 10.10.24 15:32, Diogo Ivo wrote:
>>>
>>> Somewhere between 6.11-rc4 and 6.11-rc5 the following error message is displayed
>>> when trying to initialize a nvc0_screen on the Tegra X1's
2023 Jan 27
3
[REGRESSION] GM20B probe fails after commit 2541626cfb79
On Fri, 20 Jan 2023 at 21:37, Diogo Ivo <diogo.ivo at tecnico.ulisboa.pt> wrote:
>
> On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo at tecnico.ulisboa.pt> wrote:
> > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > > As a quick check can you try changing
> >