From: Chunfeng Yun <chunfeng.yun@mediatek.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devicetree@vger.kernel.org,
Nicolas Boichat <drinkcat@chromium.org>,
Mathias Nyman <mathias.nyman@intel.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
linux-mediatek@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
Ikjoon Jang <ikjn@chromium.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH v2 1/3] dt-bindings: usb: mtk-xhci: add compatible for mt8195
Date: Sun, 7 Feb 2021 10:10:33 +0800 [thread overview]
Message-ID: <1612663833.5147.19.camel@mhfsdcap03> (raw)
In-Reply-To: <YBp7hnyPJwgK598V@kroah.com>
On Wed, 2021-02-03 at 11:31 +0100, Greg Kroah-Hartman wrote:
> On Wed, Feb 03, 2021 at 06:26:40PM +0800, Chunfeng Yun wrote:
> > There are 4 USB controllers on MT8195, the controllers (IP1~IP3,
> > exclude IP0) have a wrong default SOF/ITP interval which is
> > calculated from the frame counter clock 24Mhz by default, but
> > in fact, the frame counter clock is 48Mhz, so we should set
> > the accurate interval according to 48Mhz. Here add a new compatible
> > for MT8195, it's also supported in driver. But the first controller
> > (IP0) has no such issue, we prefer to use generic compatible,
> > e.g. mt8192's compatible.
> >
> > Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
> > ---
> > v2: no changes
>
> Note, I do not apply patches with "RFC" as obviously you do not think
> they are worthy of being applied. I don't see what you are asking to be
> done with this set of patches, please explain?
The DTS patch [2/3] in the series will cause merge conflict, due to the
dependent patches are not upstreamed.
Another problem is that I wander to know whether the compatible usage as
following is allowed:
arch/arm64/boot/dts/mediatek/mt8195.dtsi
usb@11200000 { // ip0
compatible = "mediatek,mt8192-xhci", // here use mt8192's
compatible, avoid changing SOF/ITP interval for ip0, because it's
default value is ok."mediatek,mt8192-xhci" is not supported in driver,
so finally will use generic copatible "mediatek,mtk-xhci".
"mediatek,mtk-xhci";
....
};
usb@11290000 { // ip1
compatible = "mediatek,mt8195-xhci", // here use mt8195's
compatible, used to change SOF/ITP interval, due the the wrong default
value.
"mediatek,mtk-xhci";
};
usb@112a0000 { // ip2
compatible = "mediatek,mt8195-xhci", // same as ip1
"mediatek,mtk-xhci";
};
Thank you
>
> thanks,
>
> greg k-h
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Chunfeng Yun <chunfeng.yun@mediatek.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Mathias Nyman <mathias.nyman@intel.com>,
<linux-usb@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, Ikjoon Jang <ikjn@chromium.org>,
"Nicolas Boichat" <drinkcat@chromium.org>
Subject: Re: [RFC PATCH v2 1/3] dt-bindings: usb: mtk-xhci: add compatible for mt8195
Date: Sun, 7 Feb 2021 10:10:33 +0800 [thread overview]
Message-ID: <1612663833.5147.19.camel@mhfsdcap03> (raw)
In-Reply-To: <YBp7hnyPJwgK598V@kroah.com>
On Wed, 2021-02-03 at 11:31 +0100, Greg Kroah-Hartman wrote:
> On Wed, Feb 03, 2021 at 06:26:40PM +0800, Chunfeng Yun wrote:
> > There are 4 USB controllers on MT8195, the controllers (IP1~IP3,
> > exclude IP0) have a wrong default SOF/ITP interval which is
> > calculated from the frame counter clock 24Mhz by default, but
> > in fact, the frame counter clock is 48Mhz, so we should set
> > the accurate interval according to 48Mhz. Here add a new compatible
> > for MT8195, it's also supported in driver. But the first controller
> > (IP0) has no such issue, we prefer to use generic compatible,
> > e.g. mt8192's compatible.
> >
> > Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
> > ---
> > v2: no changes
>
> Note, I do not apply patches with "RFC" as obviously you do not think
> they are worthy of being applied. I don't see what you are asking to be
> done with this set of patches, please explain?
The DTS patch [2/3] in the series will cause merge conflict, due to the
dependent patches are not upstreamed.
Another problem is that I wander to know whether the compatible usage as
following is allowed:
arch/arm64/boot/dts/mediatek/mt8195.dtsi
usb@11200000 { // ip0
compatible = "mediatek,mt8192-xhci", // here use mt8192's
compatible, avoid changing SOF/ITP interval for ip0, because it's
default value is ok."mediatek,mt8192-xhci" is not supported in driver,
so finally will use generic copatible "mediatek,mtk-xhci".
"mediatek,mtk-xhci";
....
};
usb@11290000 { // ip1
compatible = "mediatek,mt8195-xhci", // here use mt8195's
compatible, used to change SOF/ITP interval, due the the wrong default
value.
"mediatek,mtk-xhci";
};
usb@112a0000 { // ip2
compatible = "mediatek,mt8195-xhci", // same as ip1
"mediatek,mtk-xhci";
};
Thank you
>
> thanks,
>
> greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Chunfeng Yun <chunfeng.yun@mediatek.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devicetree@vger.kernel.org,
Nicolas Boichat <drinkcat@chromium.org>,
Mathias Nyman <mathias.nyman@intel.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
linux-mediatek@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
Ikjoon Jang <ikjn@chromium.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH v2 1/3] dt-bindings: usb: mtk-xhci: add compatible for mt8195
Date: Sun, 7 Feb 2021 10:10:33 +0800 [thread overview]
Message-ID: <1612663833.5147.19.camel@mhfsdcap03> (raw)
In-Reply-To: <YBp7hnyPJwgK598V@kroah.com>
On Wed, 2021-02-03 at 11:31 +0100, Greg Kroah-Hartman wrote:
> On Wed, Feb 03, 2021 at 06:26:40PM +0800, Chunfeng Yun wrote:
> > There are 4 USB controllers on MT8195, the controllers (IP1~IP3,
> > exclude IP0) have a wrong default SOF/ITP interval which is
> > calculated from the frame counter clock 24Mhz by default, but
> > in fact, the frame counter clock is 48Mhz, so we should set
> > the accurate interval according to 48Mhz. Here add a new compatible
> > for MT8195, it's also supported in driver. But the first controller
> > (IP0) has no such issue, we prefer to use generic compatible,
> > e.g. mt8192's compatible.
> >
> > Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
> > ---
> > v2: no changes
>
> Note, I do not apply patches with "RFC" as obviously you do not think
> they are worthy of being applied. I don't see what you are asking to be
> done with this set of patches, please explain?
The DTS patch [2/3] in the series will cause merge conflict, due to the
dependent patches are not upstreamed.
Another problem is that I wander to know whether the compatible usage as
following is allowed:
arch/arm64/boot/dts/mediatek/mt8195.dtsi
usb@11200000 { // ip0
compatible = "mediatek,mt8192-xhci", // here use mt8192's
compatible, avoid changing SOF/ITP interval for ip0, because it's
default value is ok."mediatek,mt8192-xhci" is not supported in driver,
so finally will use generic copatible "mediatek,mtk-xhci".
"mediatek,mtk-xhci";
....
};
usb@11290000 { // ip1
compatible = "mediatek,mt8195-xhci", // here use mt8195's
compatible, used to change SOF/ITP interval, due the the wrong default
value.
"mediatek,mtk-xhci";
};
usb@112a0000 { // ip2
compatible = "mediatek,mt8195-xhci", // same as ip1
"mediatek,mtk-xhci";
};
Thank you
>
> thanks,
>
> greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-07 2:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 10:26 [RFC PATCH v2 1/3] dt-bindings: usb: mtk-xhci: add compatible for mt8195 Chunfeng Yun
2021-02-03 10:26 ` Chunfeng Yun
2021-02-03 10:26 ` Chunfeng Yun
2021-02-03 10:26 ` [RFC PATCH v2 2/3] usb: xhci-mtk: modify the SOF/ITP interval " Chunfeng Yun
2021-02-03 10:26 ` Chunfeng Yun
2021-02-03 10:26 ` Chunfeng Yun
2021-02-07 2:27 ` Chunfeng Yun
2021-02-07 2:27 ` Chunfeng Yun
2021-02-07 2:27 ` Chunfeng Yun
2021-02-08 11:43 ` Mathias Nyman
2021-02-08 11:43 ` Mathias Nyman
2021-02-08 11:43 ` Mathias Nyman
2021-02-22 5:50 ` Chunfeng Yun
2021-02-22 5:50 ` Chunfeng Yun
2021-02-22 5:50 ` Chunfeng Yun
2021-02-03 10:26 ` [RFC PATCH v2 3/3] arm64: dts: mt8195: add USB related nodes Chunfeng Yun
2021-02-03 10:26 ` Chunfeng Yun
2021-02-03 10:26 ` Chunfeng Yun
2021-02-03 10:31 ` [RFC PATCH v2 1/3] dt-bindings: usb: mtk-xhci: add compatible for mt8195 Greg Kroah-Hartman
2021-02-03 10:31 ` Greg Kroah-Hartman
2021-02-03 10:31 ` Greg Kroah-Hartman
2021-02-07 2:10 ` Chunfeng Yun [this message]
2021-02-07 2:10 ` Chunfeng Yun
2021-02-07 2:10 ` Chunfeng Yun
2021-02-05 9:09 ` Greg Kroah-Hartman
2021-02-05 9:09 ` Greg Kroah-Hartman
2021-02-05 9:09 ` Greg Kroah-Hartman
2021-02-10 21:58 ` Rob Herring
2021-02-10 21:58 ` Rob Herring
2021-02-10 21:58 ` Rob Herring
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=1612663833.5147.19.camel@mhfsdcap03 \
--to=chunfeng.yun@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@chromium.org \
--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=robh+dt@kernel.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.