From: Jung Daehwan <dh10.jung@samsung.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Mathias Nyman <mathias.nyman@intel.com>,
Felipe Balbi <balbi@kernel.org>,
"open list:USB SUBSYSTEM" <linux-usb@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/5] dt-bindings: usb: snps,dwc3: Add 'snps,xhci-write-64-hi-lo-quirk' quirk
Date: Mon, 3 Jun 2024 17:36:57 +0900 [thread overview]
Message-ID: <20240603083657.GE23593@ubuntu> (raw)
In-Reply-To: <eb13e81c-2669-4e82-86eb-d61203475962@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]
On Mon, Jun 03, 2024 at 08:57:16AM +0200, Krzysztof Kozlowski wrote:
> On 03/06/2024 05:03, Jung Daehwan wrote:
> > On Fri, May 31, 2024 at 10:10:30AM +0200, Krzysztof Kozlowski wrote:
> >> On 31/05/2024 08:07, Daehwan Jung wrote:
> >>> Add a new quirk for dwc3 core to support writing high-low order.
> >>
> >> This does not tell me more. Could be OS property as well... please
> >> describe hardware and provide rationale why this is suitable for
> >> bindings (also cannot be deduced from compatible).
> >>
> >>
> >
> > Hi,
> >
> > I'm sorry I didn't describe it in dt-bindings patches.
> > It's described in cover-letter and other patches except in dt-bindings.
> > I will add it in next submission.
> >
> > I've found out the limitation of Synopsys dwc3 controller. This can work
> > on Host mode using xHCI. A Register related to ERST should be written
> > high-low order not low-high order. Registers are always written low-high order
> > following xHCI spec.(64-bit written is done in each 2 of 32-bit)
> > That's why new quirk is needed for workaround. This quirk is used not in
> > dwc3 controller itself, but passed to xhci quirk eventually. That's because
> > this issue occurs in Host mode using xHCI.
> >
>
> If there is only one register then you should just program it
> differently and it does not warrant quirk property.
>
Could you tell me why you think it does not warrant? I think this is
good to use quirk.
Best Regards,
Jung Deahwan
> Best regards,
> Krzysztof
>
>
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2024-06-03 8:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240531060711epcas2p4ee3987a647f6a49b589b783d14ea25ae@epcas2p4.samsung.com>
2024-05-31 6:07 ` [PATCH v2 0/5] usb: Add quirk for writing high-low order Daehwan Jung
2024-05-31 6:07 ` [PATCH v2 1/5] dt-bindings: usb: snps,dwc3: Add 'snps,xhci-write-64-hi-lo-quirk' quirk Daehwan Jung
2024-05-31 8:10 ` Krzysztof Kozlowski
2024-06-03 3:03 ` Jung Daehwan
2024-06-03 6:57 ` Krzysztof Kozlowski
2024-06-03 8:36 ` Jung Daehwan [this message]
2024-06-04 6:19 ` Krzysztof Kozlowski
2024-05-31 6:07 ` [PATCH v2 2/5] usb: dwc3: Support quirk for writing high-low order Daehwan Jung
2024-06-04 0:16 ` Thinh Nguyen
2024-06-04 1:59 ` Jung Daehwan
2024-05-31 6:07 ` [PATCH v2 3/5] dt-bindings: usb: xhci: Add 'write-64-hi-lo-quirk' quirk Daehwan Jung
2024-05-31 8:12 ` Krzysztof Kozlowski
2024-06-03 3:34 ` Jung Daehwan
2024-06-03 6:58 ` Krzysztof Kozlowski
2024-06-03 8:25 ` Jung Daehwan
2024-06-04 0:30 ` Thinh Nguyen
2024-06-04 2:19 ` Jung Daehwan
2024-05-31 6:07 ` [PATCH v2 4/5] xhci: Add a quirk for writing ERST in high-low order Daehwan Jung
2024-05-31 6:07 ` [PATCH v2 5/5] usb: host: xhci-plat: Add support for XHCI_WRITE_64_HI_LO_QUIRK Daehwan Jung
2024-05-31 8:12 ` Krzysztof Kozlowski
2024-06-03 3:44 ` Jung Daehwan
2024-06-03 6:56 ` Krzysztof Kozlowski
2024-06-03 8:51 ` Jung Daehwan
2024-06-04 6:20 ` Krzysztof Kozlowski
2024-06-05 1:50 ` Jung Daehwan
2024-06-05 6:44 ` Krzysztof Kozlowski
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=20240603083657.GE23593@ubuntu \
--to=dh10.jung@samsung.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=balbi@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=robh@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.