From: Rob Clark <robdclark@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>, Dave Airlie <airlied@gmail.com>
Cc: Akhil P Oommen <akhilpo@codeaurora.org>,
freedreno <freedreno@lists.freedesktop.org>,
dri-devel@freedesktop.org,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jordan Crouse <jcrouse@codeaurora.org>,
Sharat Masetty <smasetty@codeaurora.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Matthias Kaehlcke <mka@chromium.org>,
saravanak@google.com, Sibi Sankar <sibis@codeaurora.org>,
Jonathan <jonathan@marek.ca>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: [PATCH v5 0/6] Add support for GPU DDR BW scaling
Date: Thu, 30 Jul 2020 14:26:08 -0700 [thread overview]
Message-ID: <CAF6AEGv-e5KdbcDcst=y+h-uhDa4sKKEMoGuA88bvZ_1i46RLQ@mail.gmail.com> (raw)
In-Reply-To: <20200730153722.cnpg6n6tnmvjtuso@vireshk-mac-ubuntu>
On Thu, Jul 30, 2020 at 8:37 AM Viresh Kumar <viresh.kumar@linaro.org> wrote:
>
> On 30-07-20, 08:27, Rob Clark wrote:
> > Hmm, I've already sent my pull request to Dave, dropping the patch
> > would require force-push and sending a new PR. Which I can do if Dave
> > prefers. OTOH I guess it isn't the end of the world if the patch is
> > merged via two different trees.
>
> I don't think a patch can go via two trees, as that would have two sha
> keys for the same code.
>
> Though it is fine for a patch to go via two different trees if we make
> sure the same sha key is used for both.
>
> Will it be possible for you to provide a branch/tag of your branch
> that I can base stuff of ?
>
Ok, I sent a v2 pull req that dropped the OPP patch. Both are tagged
so Dave can use either version, so I guess you two can coordinate this
BR,
-R
WARNING: multiple messages have this Message-ID (diff)
From: Rob Clark <robdclark@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>, Dave Airlie <airlied@gmail.com>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, Jonathan <jonathan@marek.ca>,
saravanak@google.com,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Sharat Masetty <smasetty@codeaurora.org>,
Akhil P Oommen <akhilpo@codeaurora.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Matthias Kaehlcke <mka@chromium.org>,
dri-devel@freedesktop.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
freedreno <freedreno@lists.freedesktop.org>,
Sibi Sankar <sibis@codeaurora.org>
Subject: Re: [PATCH v5 0/6] Add support for GPU DDR BW scaling
Date: Thu, 30 Jul 2020 14:26:08 -0700 [thread overview]
Message-ID: <CAF6AEGv-e5KdbcDcst=y+h-uhDa4sKKEMoGuA88bvZ_1i46RLQ@mail.gmail.com> (raw)
In-Reply-To: <20200730153722.cnpg6n6tnmvjtuso@vireshk-mac-ubuntu>
On Thu, Jul 30, 2020 at 8:37 AM Viresh Kumar <viresh.kumar@linaro.org> wrote:
>
> On 30-07-20, 08:27, Rob Clark wrote:
> > Hmm, I've already sent my pull request to Dave, dropping the patch
> > would require force-push and sending a new PR. Which I can do if Dave
> > prefers. OTOH I guess it isn't the end of the world if the patch is
> > merged via two different trees.
>
> I don't think a patch can go via two trees, as that would have two sha
> keys for the same code.
>
> Though it is fine for a patch to go via two different trees if we make
> sure the same sha key is used for both.
>
> Will it be possible for you to provide a branch/tag of your branch
> that I can base stuff of ?
>
Ok, I sent a v2 pull req that dropped the OPP patch. Both are tagged
so Dave can use either version, so I guess you two can coordinate this
BR,
-R
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-07-30 21:25 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 12:41 [PATCH v5 0/6] Add support for GPU DDR BW scaling Akhil P Oommen
2020-07-13 12:41 ` Akhil P Oommen
2020-07-13 12:41 ` [PATCH v5 1/6] dt-bindings: drm/msm/gpu: Document gpu opp table Akhil P Oommen
2020-07-13 12:41 ` Akhil P Oommen
2020-07-13 12:41 ` [PATCH v5 2/6] drm: msm: a6xx: send opp instead of a frequency Akhil P Oommen
2020-07-13 12:41 ` Akhil P Oommen
2020-07-13 12:41 ` [PATCH v5 3/6] drm: msm: a6xx: use dev_pm_opp_set_bw to scale DDR Akhil P Oommen
2020-07-13 12:41 ` Akhil P Oommen
2020-07-13 12:41 ` [PATCH v5 4/6] arm64: dts: qcom: SDM845: Enable GPU DDR bw scaling Akhil P Oommen
2020-07-13 12:41 ` Akhil P Oommen
2020-07-13 12:41 ` [PATCH v5 5/6] arm64: dts: qcom: sc7180: Add interconnects property for GPU Akhil P Oommen
2020-07-13 12:41 ` Akhil P Oommen
2020-07-15 18:27 ` Rob Clark
2020-07-15 18:27 ` Rob Clark
2020-07-13 12:41 ` [PATCH v5 6/6] arm64: dts: qcom: sc7180: Add opp-peak-kBps to GPU opp Akhil P Oommen
2020-07-13 12:41 ` Akhil P Oommen
2020-07-15 15:36 ` [PATCH v5 0/6] Add support for GPU DDR BW scaling Rob Clark
2020-07-15 15:36 ` Rob Clark
2020-07-20 10:01 ` Viresh Kumar
2020-07-20 10:01 ` Viresh Kumar
2020-07-20 15:03 ` Rob Clark
2020-07-20 15:03 ` Rob Clark
2020-07-21 3:24 ` Viresh Kumar
2020-07-21 3:24 ` Viresh Kumar
2020-07-21 14:28 ` Rob Clark
2020-07-21 14:28 ` Rob Clark
2020-07-22 5:30 ` Viresh Kumar
2020-07-22 5:30 ` Viresh Kumar
2020-07-22 15:47 ` Rob Clark
2020-07-22 15:47 ` Rob Clark
2020-07-22 23:01 ` Daniel Vetter
2020-07-22 23:01 ` Daniel Vetter
2020-07-30 5:10 ` Viresh Kumar
2020-07-30 5:10 ` Viresh Kumar
2020-07-30 15:27 ` Rob Clark
2020-07-30 15:27 ` Rob Clark
2020-07-30 15:37 ` Viresh Kumar
2020-07-30 15:37 ` Viresh Kumar
2020-07-30 15:46 ` Rob Clark
2020-07-30 15:46 ` Rob Clark
2020-07-30 21:26 ` Rob Clark [this message]
2020-07-30 21:26 ` Rob Clark
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='CAF6AEGv-e5KdbcDcst=y+h-uhDa4sKKEMoGuA88bvZ_1i46RLQ@mail.gmail.com' \
--to=robdclark@gmail.com \
--cc=airlied@gmail.com \
--cc=akhilpo@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jcrouse@codeaurora.org \
--cc=jonathan@marek.ca \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=saravanak@google.com \
--cc=sibis@codeaurora.org \
--cc=smasetty@codeaurora.org \
--cc=viresh.kumar@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.