From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: neil.armstrong@linaro.org, Marek Vasut <marex@denx.de>,
Tom Rini <trini@konsulko.com>, Lukasz Majewski <lukma@denx.de>,
Bin Meng <bmeng.cn@gmail.com>
Cc: Caleb Connolly <caleb.connolly@linaro.org>,
u-boot-qcom@groups.io, u-boot@lists.denx.de
Subject: Re: [PATCH v2 0/3] dwc3: gadget: properly fix cache operations
Date: Tue, 01 Oct 2024 17:01:47 +0200 [thread overview]
Message-ID: <877cardfz8.fsf@baylibre.com> (raw)
In-Reply-To: <1b12b2ba-9f4a-4535-8ab3-134975fd3a25@linaro.org>
On mar., oct. 01, 2024 at 16:43, Neil Armstrong <neil.armstrong@linaro.org> wrote:
> Hi,
>
> On 24/07/2024 17:48, Neil Armstrong wrote:
>> We experience huge problems with cache handling on Qualcomm
>> systems, and it appears the dcache handling in the DWC3 gadget
>> code is quite wrong and causes operational issues.
>>
>> This serie fixes the dcache operations on unaligned data,
>> and properly invalidate buffers when reading back data from
>> hardware.
>>
>> Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
>> ---
>> Changes in v2:
>> - Fix typo in drivers/usb/dwc3/core.h and rewrite patch 1 commit message
>> - Link to v1: https://lore.kernel.org/r/20240719-u-boot-dwc3-gadget-dcache-fixup-v1-0-58a5f026ea8e@linaro.org
>>
>> ---
>> Neil Armstrong (3):
>> usb: dwc3: allocate setup_buf with dma_alloc_coherent()
>> usb: dwc3: fix dcache flush range calculation
>> usb: dwc3: invalidate dcache on buffer used in interrupt handling
>>
>> drivers/usb/dwc3/core.h | 2 ++
>> drivers/usb/dwc3/ep0.c | 6 ++++--
>> drivers/usb/dwc3/gadget.c | 10 ++++++----
>> drivers/usb/dwc3/io.h | 13 ++++++++++++-
>> 4 files changed, 24 insertions(+), 7 deletions(-)
>> ---
>> base-commit: 3f772959501c99fbe5aa0b22a36efe3478d1ae1c
>> change-id: 20240719-u-boot-dwc3-gadget-dcache-fixup-ea1e92758663
>>
>> Best regards,
>
> Gentle ping, those fixes are quite important to make USB Gadget reliable
> on Qualcomm platforms,
Sorry for the wait on this one. I did not act upon this series because
it's not assigned to me.
According to patchwork [1], this is assigned to bmeng.
Bin, do you want to review this or can I pick this up through u-boot-dfu
since it's usb gadget related?
[1] https://patchwork.ozlabs.org/project/uboot/cover/20240724-u-boot-dwc3-gadget-dcache-fixup-v2-0-65836d699a71@linaro.org/
Thanks,
Mattijs
>
> Thanks,
> Neil
prev parent reply other threads:[~2024-10-01 15:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 15:48 [PATCH v2 0/3] dwc3: gadget: properly fix cache operations Neil Armstrong
2024-07-24 15:48 ` [PATCH v2 1/3] usb: dwc3: allocate setup_buf with dma_alloc_coherent() Neil Armstrong
2024-07-24 15:48 ` [PATCH v2 2/3] usb: dwc3: fix dcache flush range calculation Neil Armstrong
2024-10-01 15:21 ` Marek Vasut
2024-10-01 15:32 ` Neil Armstrong
2024-10-01 15:47 ` Marek Vasut
2024-10-02 7:31 ` neil.armstrong
2024-07-24 15:48 ` [PATCH v2 3/3] usb: dwc3: invalidate dcache on buffer used in interrupt handling Neil Armstrong
2024-10-01 14:43 ` [PATCH v2 0/3] dwc3: gadget: properly fix cache operations Neil Armstrong
2024-10-01 15:01 ` Mattijs Korpershoek [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=877cardfz8.fsf@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=bmeng.cn@gmail.com \
--cc=caleb.connolly@linaro.org \
--cc=lukma@denx.de \
--cc=marex@denx.de \
--cc=neil.armstrong@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot-qcom@groups.io \
--cc=u-boot@lists.denx.de \
/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.