Brian Norris <briannorris@xxxxxxxxxxxx> writes: > On Fri, Mar 8, 2019 at 1:42 AM Kalle Valo <kvalo@xxxxxxxxxxxxxx> wrote: >> Brian Norris <briannorris@xxxxxxxxxxxx> writes: >> > On Fri, Feb 8, 2019 at 5:42 AM Kalle Valo <kvalo@xxxxxxxxxxxxxx> wrote: >> >> No replies from anyone (including Wen) for 3 months about testing this >> >> patch on anything else than QCA6174. So I'll drop this now, please >> >> resubmit once test coverage is better. >> > >> > I know this isn't exactly what you're asking for, but FWIW we've been >> > using this since late November on all our QCA6174 products. No issues >> > seen as far as I know, and we have seen some power savings. >> >> Thanks for the feedback, this is very good to know. I also would like to >> apply this but not before we have some testing feedback from AP chipsets >> like QCA988X or QCA9984. Wen, are you planning to test those and >> resubmit? > > May I ping here? We (Chromium OS) are continuing to carry this patch, > and would love to come up with something that can land upstream. If > necessary, I can rework it to apply more specifically -- e.g., only to > QCA6174 PCI IDs. Yeah, enabling only for QCA6174 sounds best. -- https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
