[alsa-devel] [PATCH 0/4] add runtime pm support for AMD display audio

Takashi Iwai tiwai at suse.de
Tue Nov 26 16:58:11 CET 2019


On Tue, 26 Nov 2019 16:31:37 +0100,
Alex Deucher wrote:
> 
> On Tue, Nov 26, 2019 at 9:53 AM Takashi Iwai <tiwai at suse.de> wrote:
> >
> > On Mon, 25 Nov 2019 15:40:43 +0100,
> > Alex Deucher wrote:
> > >
> > > On Sat, Nov 23, 2019 at 3:57 AM Takashi Iwai <tiwai at suse.de> wrote:
> > > >
> > > > On Fri, 22 Nov 2019 22:43:49 +0100,
> > > > Alex Deucher wrote:
> > > > >
> > > > > These patches were originally part of a larger set of patches
> > > > > to enabled runtime pm support on the GPU side[1].  However, the
> > > > > patches are useful on their own there are really no dependencies,
> > > > > other than the fact that you need both for runtime pm to kick in
> > > > > on the GPU side.  The GPU side will be landing for 5.6; I'd like
> > > > > to land the audio side as well.
> > > >
> > > > Do you mean that these can go into 5.5-rc1, or they need waiting until
> > > > 5.5-rc1 release?  I guess these won't break things even without the
> > > > runtime PM support in GPU side, as the ELD notification is done via
> > > > audio component, so I'm fine to apply them at any time.
> > >
> > > Up to you.  I'm ok to wait for the next merge window if you'd prefer.
> >
> > OK, I'm going to apply them for 5.5-rc1 inclusion.
> >
> > BTW, should I apply these patches with your gmail address as author
> > (while sign-off is AMD address)?  Or should I align both to your AMD
> > address?
> >
> > It's nothing wrong to have different addresses in the commit, but if
> > unintended, it's better to align both.
> 
> I guess my AMD address.  I usually use my gmail address for sending
> patches out of laziness.

OK, now merged all four patches.

thanks,

Takashi


More information about the Alsa-devel mailing list