From: Chunfeng Yun <chunfeng.yun@mediatek.com>
To: Ikjoon Jang <ikjn@chromium.org>
Cc: "moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>, <linux-usb@vger.kernel.org>,
"Zhanyong Wang" <zhanyong.wang@mediatek.com>,
Tianping Fang <tianping.fang@mediatek.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mathias Nyman <mathias.nyman@intel.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] Release allocated periodic bandwidth data from reset_bandwidth()
Date: Mon, 14 Dec 2020 11:24:49 +0800 [thread overview]
Message-ID: <1607916289.23328.21.camel@mhfsdcap03> (raw)
In-Reply-To: <CAATdQgBZn3oehw_20D3yMmDA8G61oMHVax8LqJ-hPQv+9kJGLQ@mail.gmail.com>
On Fri, 2020-12-11 at 14:36 +0800, Ikjoon Jang wrote:
> On Fri, Dec 11, 2020 at 9:53 AM Chunfeng Yun <chunfeng.yun@mediatek.com> wrote:
> >
> > On Thu, 2020-12-10 at 18:47 +0800, Ikjoon Jang wrote:
> > > xhci-mtk releases allocated TT bandwidth data only when whole
> > > endpoints of a device are dropped as there're only {add|drop}_endpoint()
> > > hooks are defined. This patchset adds more hooks and releases all
> > > bandwidth data from reset_bandwidth() path, not drop_endpoint().
> > >
> > >
> > > Changes in v2:
> > > - fix a 0-day warning from unused variable
> > > - split one big patch into three patches
> > > - bugfix in hw flags
> > >
> > > Ikjoon Jang (3):
> > > usb: xhci-mtk: code cleanups in getting bandwidth table
> > > usb: xhci-mtk: delay association of tt and ep
> > > usb: xhci-mtk: fix unreleased bandwidth data
> > >
> > > drivers/usb/host/xhci-mtk-sch.c | 180 ++++++++++++++++++++------------
> > > drivers/usb/host/xhci-mtk.h | 13 +++
> > > drivers/usb/host/xhci.c | 9 ++
> > > 3 files changed, 133 insertions(+), 69 deletions(-)
> > Thanks for your patch, I'll test it and check it with our DE
>
> Thanks, I will upload v3.
> But I don't expect any logic changes from v2.
> Can you please give me feedback on v2 if you find anything?
Ok
>
> >
> > >
> >
prev parent reply other threads:[~2020-12-14 3:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 10:47 [PATCH v2 0/3] Release allocated periodic bandwidth data from reset_bandwidth() Ikjoon Jang
2020-12-10 10:47 ` [PATCH v2 1/3] usb: xhci-mtk: code cleanups in getting bandwidth table Ikjoon Jang
2020-12-10 10:47 ` [PATCH v2 2/3] usb: xhci-mtk: delay association of tt and ep Ikjoon Jang
2020-12-10 10:59 ` Greg Kroah-Hartman
2020-12-10 10:47 ` [PATCH v2 3/3] usb: xhci-mtk: fix unreleased bandwidth data Ikjoon Jang
2020-12-10 10:58 ` Greg Kroah-Hartman
2020-12-11 6:27 ` Ikjoon Jang
2020-12-11 1:53 ` [PATCH v2 0/3] Release allocated periodic bandwidth data from reset_bandwidth() Chunfeng Yun
2020-12-11 6:36 ` Ikjoon Jang
2020-12-14 3:24 ` Chunfeng Yun [this message]
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=1607916289.23328.21.camel@mhfsdcap03 \
--to=chunfeng.yun@mediatek.com \
--cc=gregkh@linuxfoundation.org \
--cc=ikjn@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=matthias.bgg@gmail.com \
--cc=tianping.fang@mediatek.com \
--cc=zhanyong.wang@mediatek.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;
as well as URLs for NNTP newsgroup(s).