From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Greg Malysa <greg.malysa@timesys.com>
Cc: Marek Vasut <marex@denx.de>,
u-boot@lists.denx.de,
Nathan Barrett-Morrison <nathan.morrison@timesys.com>,
Ian Roberts <ian.roberts@timesys.com>,
Jonas Karlman <jonas@kwiboo.se>, Simon Glass <sjg@chromium.org>,
Teik Heng Chong <teik.heng.chong@intel.com>,
Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH] usb: dwc2: Add in version 4xx compatibility
Date: Tue, 23 Apr 2024 09:09:04 +0200 [thread overview]
Message-ID: <874jbs7dyn.fsf@baylibre.com> (raw)
In-Reply-To: <CAAjXUaqYv1zTATXhU5GeOMpSCK-HMxvMW5_edbotZ8TUczcVMA@mail.gmail.com>
Hi Greg,
On ven., avril 19, 2024 at 15:21, Greg Malysa <greg.malysa@timesys.com> wrote:
> Hi Mattijs,
>
>> Please avoid top-posting when replying, it makes following the
>> discussion more difficult:
>> https://www.kernel.org/doc/html/latest/process/submitting-patches.html#use-trimmed-interleaved-replies-in-email-discussions
>
> Will do. Sorry about that; I'm still learning about this approach to email.
No worries. There are quite some things to learn and we probably all did
this wrong when starting. Thank you for taking the time to learn and to contribute!
>
>> Looking at
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=65dc2e725286106f99c6f6b78e3d9c52c15f3a9c
>>
>> we can see that the following is added:
>> #define DWC2_CORE_REV_MASK 0x0000ffff
>>
>> This makes me believe that the versioning follows a well known pattern.
>
> I can submit a v2 next week to bring it in line with the kernel's approach.
To me, it's fine as is.
>
>> Note that this change is also part of:
>> https://lore.kernel.org/all/20240328131811.94559-1-seashell11234455@gmail.com/
>
> Or if you prefer I can also drop our patch and we can pursue this
> linked patch with both 4xx compatibility and the 420a reset handling.
I think the patch you submitted is fine by itself, but I'd let Marek
decide since he is the maintainer for this part.
If you have access to the hardware that has a 4.20a dwc2 controller,
maybe you can help testing the patch above patch as well?
>
> Thanks,
> Greg
next prev parent reply other threads:[~2024-04-23 7:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 2:32 [PATCH] usb: dwc2: Add in version 4xx compatibility Greg Malysa
2024-03-26 11:50 ` Marek Vasut
2024-03-26 15:36 ` Greg Malysa
2024-04-16 9:06 ` Mattijs Korpershoek
2024-04-19 19:21 ` Greg Malysa
2024-04-23 7:09 ` Mattijs Korpershoek [this message]
2024-04-23 22:31 ` Marek Vasut
2024-05-07 7:32 ` Greg Malysa
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=874jbs7dyn.fsf@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=greg.malysa@timesys.com \
--cc=ian.roberts@timesys.com \
--cc=jonas@kwiboo.se \
--cc=marex@denx.de \
--cc=nathan.morrison@timesys.com \
--cc=sjg@chromium.org \
--cc=teik.heng.chong@intel.com \
--cc=trini@konsulko.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox