public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Michael Turquette <mturquette@baylibre.com>
Cc: Rob Clark <robdclark@gmail.com>,
	linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] clk: qocm: add qcom_cc_map_norequest
Date: Mon, 08 Jul 2024 15:30:22 -0700	[thread overview]
Message-ID: <5153b8f8a6c6ffdc1254e00c47a888ed.sboyd@kernel.org> (raw)
In-Reply-To: <20240628-gpucc-no-request-v1-1-b680c2f90817@linaro.org>

Quoting Dmitry Baryshkov (2024-06-27 22:20:22)
> The GPU clock controllers use memory region that is a part of the GMU's
> memory region. Add qcom_cc_map_norequest() to be used by GPUCC, so that
> GPU driver can use devm_ioremap_resource for GMU resources.

Why does GMU map the gpu clk controller? Does it use those registers? We
don't want to allow two different drivers to map the same region because
then they don't coordinate and write over things.

  reply	other threads:[~2024-07-08 22:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28  5:20 [PATCH 0/2] clk: qcom: gpucc-*: stop requesting register resource Dmitry Baryshkov
2024-06-28  5:20 ` [PATCH 1/2] clk: qocm: add qcom_cc_map_norequest Dmitry Baryshkov
2024-07-08 22:30   ` Stephen Boyd [this message]
2024-07-10 23:32     ` Dmitry Baryshkov
2024-07-11  0:04       ` Stephen Boyd
2024-07-11  8:19         ` Dmitry Baryshkov
2024-06-28  5:20 ` [PATCH 2/2] clk: qcom: gpucc-*: use qcom_cc_map_norequest Dmitry Baryshkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5153b8f8a6c6ffdc1254e00c47a888ed.sboyd@kernel.org \
    --to=sboyd@kernel.org \
    --cc=andersson@kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robdclark@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox