On Tue, Apr 11, 2023 at 8:00 AM Daniel Vetter wrote:
>
> On Tue, Apr 11, 2023 at 07:55:33AM -0700, Rob Clark wrote:
> > On Tue, Apr 11, 2023 at 3:27 AM Daniel Vetter wrote:
> > > > Konrad Dybcio (18):
> > > > drm/msm/adreno: Use OPP for every GPU generation
> > >
> > > This had a minor
On Tue, Apr 11, 2023 at 07:55:33AM -0700, Rob Clark wrote:
> On Tue, Apr 11, 2023 at 3:27 AM Daniel Vetter wrote:
> > > Konrad Dybcio (18):
> > > drm/msm/adreno: Use OPP for every GPU generation
> >
> > This had a minor conflict with refactoring from drm-misc-next, I went
> > what's in your
On Tue, Apr 11, 2023 at 3:27 AM Daniel Vetter wrote:
>
> On Mon, Apr 10, 2023 at 07:50:50AM -0700, Rob Clark wrote:
> > Hi Dave,
> >
> > This is the main pull for v6.4, see below for description. A bit big
> > this time because of (1) generated header updates and (2) dpu hw
> > catelog rework
On Mon, Apr 10, 2023 at 07:50:50AM -0700, Rob Clark wrote:
> Hi Dave,
>
> This is the main pull for v6.4, see below for description. A bit big
> this time because of (1) generated header updates and (2) dpu hw
> catelog rework which split the increasingly unwieldy
> big-giant-file-of-tables into
Hi Dave,
This is the main pull for v6.4, see below for description. A bit big
this time because of (1) generated header updates and (2) dpu hw
catelog rework which split the increasingly unwieldy
big-giant-file-of-tables into per-SoC files. But those are mainly
mechanical churn.
The following
