gpu: nvgpu: dbg level for per-write ctx patch msg

The message "per-write ctx patch begin?" is a legacy message for warning
about probably inefficient code, but it's written at error loglevel.
Silence it out a bit by using gk20a_dbg_info(). The inefficient paths
can be fixed later.

Bug 200075565

Change-Id: Idae821aef3001ea5016de22a1a87fec747c42d31
Signed-off-by: Konsta Holtta <kholtta@nvidia.com>
Reviewed-on: http://git-master/r/734248

1 files changed, 1 insertions, 2 deletions

diff --git a/drivers/gpu/nvgpu/gk20a/gr_gk20a.c b/drivers/gpu/nvgpu/gk20a/gr_gk20a.c
index 4a98514b..b709a980 100644
--- a/drivers/gpu/nvgpu/gk20a/gr_gk20a.c
+++ b/drivers/gpu/nvgpu/gk20a/gr_gk20a.c
@@ -644,8 +644,7 @@ int gr_gk20a_ctx_patch_write(struct gk20a *g,
                  * but be defensive still... */
                 if (!ch_ctx->patch_ctx.mem.cpu_va) {
                         int err;
-                        gk20a_err(dev_from_gk20a(g),
-                                   "per-write ctx patch begin?");
+                        gk20a_dbg_info("per-write ctx patch begin?");
                         /* yes, gr_gk20a_ctx_patch_smpc causes this one */
                         err = gr_gk20a_ctx_patch_write_begin(g, ch_ctx);
                         if (err)