usb: device_next: Simple NCM driver for usb-next #72310

rgrr · 2024-05-04T06:28:24Z

This is a first version of an NCM driver for usb-next. As a template the usb-next ECM driver has been used.

The driver has been kept very simple (one datagram per NTB and one buffer per direction). Current idea is not to optimize performance, focus is more on existence of an NCM driver for Zephyr.

To make the driver work with iperf (my testcase), CONFIG_NET_BUF_VARIABLE_DATA_SIZE=y must be used.

Discussion about this PR can be found in #71451.

Resolves: #71451

josuah

This is a recent modification on upstream Zephyr: usbd_contex had a typo and was adjusted to usbd_context.

8d344cc

josuah · 2024-07-01T20:03:29Z

To help with maintenance and troubleshooting, I believe Zephyr maintainers like to have only meaningful commits.
Maybe making a single commit that introduces the class would work?

git rebase -i HEAD^4 and modifying the lines for the two commits that needs to be changed from pick to squash would likely work.

rgrr · 2024-07-02T05:41:07Z

This is a recent modification on upstream Zephyr: usbd_contex had a typo and was adjusted to usbd_context.

Haha... first time I couldn't compile before pushing, because my environment was broken (see eclipse-cdt/cdt#846). And then the CI shows you that that's a bad idea.

Squashed the commits (again). I actually don't like that, because history is lost (and actually I'm not a fan of rebasing because history is rewritten, but that is another story...))

jfischer-no · 2024-07-08T14:46:23Z

doc/connectivity/usb/device_next/usb_device.rst

Please move changes in doc/connectivity/usb/device_next/usb_device.rst to a separate commit, it would also make it easier for you to rebase.

ok... I have created three branches and soon two more PRs will appear here. New code stays in this PR.

Concerning review procedure: who is resolving conversations? You? Me?

One branch (one PR) with N commits is the preferred way.

gosh... what have I done!? Misunderstood Johanns point completely. Will go back.

what commit comments do you expect in this case?

If by commit comments you mean the commit messages, then each commit message should describe what the individual commit does. Do not reuse the title for all of the commits, make each of them point to the respective part. For example the commit changing sample should start its commit title with samples: net: zperf:.

Things like "This PR contains the actual driver." do not belong in commit message.

jfischer-no · 2024-07-08T14:55:29Z

include/zephyr/usb/class/usb_cdc.h

I do not think you should rename it here or at all.

Hmm... but cdc_ecm_descriptor is the wrong name. Will change it back anyway

jfischer-no · 2024-07-08T14:58:03Z

samples/net/zperf/overlay-netusb.conf

This configuration overlay is not used if sample is build for the new USB device support. Stray changes?

I have to rethink why I have done this ;-)

jfischer-no · 2024-07-08T15:01:31Z

samples/net/zperf/overlay-usbd_next.conf

Please move sample changes to a separate commit.
Looks like there should be three commits in your PR, 1) USB NCM implementation + bindings, 2) sample changes, 3) doc update.

jfischer-no · 2024-07-08T15:02:47Z

samples/net/zperf/usbd_next_ncm.overlay

Please indent with tabs, always.

jfischer-no · 2024-07-08T16:27:27Z

subsys/usb/device_next/class/usbd_cdc_ncm.c

Variable definition should be at the top of a block. Please clean up and fix your code, I will continue the review after that.

jfischer-no · 2024-07-08T16:33:36Z

subsys/usb/device_next/class/usbd_cdc_ncm.c

Prefixing with _ is not okay.

jfischer-no · 2024-07-08T16:42:18Z

subsys/usb/device_next/class/usbd_cdc_ncm_internal.h

No typedefs.

jfischer-no · 2024-07-08T16:48:24Z

subsys/usb/device_next/class/usbd_cdc_ncm_internal.h

Is it not the same as just #define CFG_CDC_NCM_ALIGNMENT 4?
Please remove all the CFG_ prefixes and move whatever make sense to Kconfig options.

I have "reserved" those CFGs for future extensions. Currently there is no meaning in them, so they don't appear in Kconfig. Will change it.

jfischer-no · 2024-07-08T16:49:41Z

subsys/usb/device_next/class/usbd_cdc_ncm_internal.h

#define NTH16_SIGNATURE 0x484D434EUL #define NDP16_SIGNATURE_NCM0 0x304D434EUL #define NDP16_SIGNATURE_NCM1 0x314D434EUL

@jfischer-no : many thanks for the extensive review, I will change accordingly (or comment on it). But this will take some time.

This is a simple USB-NCM driver. It just has one NTB per direction and within the NTB only one datagram can be received/transmitted. Main goal is existance of an NCM driver, performance will follow in further steps. This PR contains the actual driver. Signed-off-by: Hardy Griech <[email protected]>

Sample changes. Signed-off-by: Hardy Griech <[email protected]>

Documentation changes. Signed-off-by: Hardy Griech <[email protected]>

jfischer-no · 2024-09-05T21:27:08Z

@rgrr There still seems to be no changes since the last review, do you have any challenges with git?

rgrr · 2024-09-06T16:17:15Z

@rgrr There still seems to be no changes since the last review, do you have any challenges with git?

No... sorry... I'm currently too busy to work on the PR. Don't drop it, if there is time I will polish it.

josuah · 2024-10-23T22:16:21Z

Following this initial effort on bringing CDC NCM to Zephyr, an independent PR was started after this message and is now merged:

usb: device_next: USB CDC NCM class implementation #79508

The outline of functions is the same, but their implementation differ in several places.
I suppose this PR content helped in giving insight in how the problem could be solved, and was supportive on the other PR which led to CDC NCM merged Zephyr.

Thank you @rgrr !
It might be possible to close this PR now, as the NCM development effort were pursued on the other PR.

rgrr · 2024-10-24T06:05:05Z

:

The outline of functions is the same, but their implementation differ in several places. I suppose this PR content helped in giving insight in how the problem could be solved, and was supportive on the other PR which led to CDC NCM merged Zephyr.

Great, if my implementation was of any help!

Thank you @rgrr ! It might be possible to close this PR now, as the NCM development effort were pursued on the other PR.

Of course close it. I will check the other implementation soon and provide comments if required.

Sorry for wasting your time for reviewing my PR.

josuah · 2024-10-24T08:55:34Z

Sorry for wasting your time for reviewing my PR

No issue at all ! I learned in the process and that was useful in other ways (UVC).

zephyrbot added area: Ethernet area: Networking area: USB Universal Serial Bus area: Samples Samples area: Devicetree Binding PR modifies or adds a Device Tree binding labels May 4, 2024

rgrr mentioned this pull request May 4, 2024

Draft: Simple NCM driver for usb-next #72305

Closed

zephyrbot requested review from decsny, galak, jfischer-no, jukkar, kartben, nashif, pdgendt, rlubos, ssharks, tbursztyka and tmon-nordic May 4, 2024 06:29

zephyrbot assigned jfischer-no May 4, 2024

rgrr mentioned this pull request May 4, 2024

Is there any interest in USB CDC-NCM driver? #71451

Closed

rgrr changed the title ~~Draft: Simple NCM driver for usb-next (2nd try)~~ Draft: usb: device_next: Simple NCM driver for usb-next (2nd try) May 4, 2024

rgrr changed the title ~~Draft: usb: device_next: Simple NCM driver for usb-next (2nd try)~~ usb: device_next: Simple NCM driver for usb-next (2nd try) May 6, 2024

rgrr force-pushed the cdc-ncm2 branch from 5819631 to 3d9c25c Compare May 7, 2024 17:22

zephyrbot requested a review from lmajewski May 7, 2024 17:23

rgrr changed the title ~~usb: device_next: Simple NCM driver for usb-next (2nd try)~~ usb: device_next: Simple NCM driver for usb-next May 8, 2024

rgrr force-pushed the cdc-ncm2 branch 2 times, most recently from a4b0e57 to 94b376e Compare May 8, 2024 11:43

rgrr requested review from JiafeiPan, anangl, dleach02 and mmahadevan108 as code owners May 8, 2024 21:38

rgrr force-pushed the cdc-ncm2 branch from a567af7 to cfd9b86 Compare June 3, 2024 06:24

rgrr force-pushed the cdc-ncm2 branch 2 times, most recently from 33e603f to 387704e Compare June 30, 2024 14:49

josuah reviewed Jul 1, 2024

View reviewed changes

rgrr force-pushed the cdc-ncm2 branch from a40f255 to ef2cfee Compare July 2, 2024 05:35

jfischer-no requested changes Jul 8, 2024

View reviewed changes

rgrr force-pushed the cdc-ncm2 branch from ef2cfee to 0cf5cc0 Compare July 9, 2024 06:19

This was referenced Jul 9, 2024

usb: device_next: Simple NCM driver for usb-next - sample changes #75632

Closed

usb: device_next: Simple NCM driver for usb-next - documentation changes #75633

Closed

josuah mentioned this pull request Jul 12, 2024

drivers: video: Add support for arducam mega #66994

Closed

rgrr force-pushed the cdc-ncm2 branch from 94583bc to d09d1a8 Compare July 24, 2024 05:53

rgrr added 3 commits July 31, 2024 07:26

usb: device_next: Simple NCM driver for usb-next

6d39c05

Sample changes. Signed-off-by: Hardy Griech <[email protected]>

usb: device_next: Simple NCM driver for usb-next

0e5407f

Documentation changes. Signed-off-by: Hardy Griech <[email protected]>

rgrr force-pushed the cdc-ncm2 branch from d09d1a8 to 0e5407f Compare July 31, 2024 05:26

carlescufi requested review from jfischer-no, josuah and tmon-nordic August 28, 2024 10:24

carlescufi mentioned this pull request Aug 28, 2024

Planned USB device/host support rework/enhancements #42066

Closed

57 tasks

rgrr marked this pull request as draft September 6, 2024 16:17

jukkar removed their request for review October 18, 2024 07:38

josuah removed their request for review October 23, 2024 22:17

josuah closed this Oct 24, 2024

usb: device_next: Simple NCM driver for usb-next #72310

usb: device_next: Simple NCM driver for usb-next #72310

Uh oh!

Conversation

rgrr commented May 4, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

josuah left a comment

Choose a reason for hiding this comment

Uh oh!

josuah commented Jul 1, 2024

Uh oh!

rgrr commented Jul 2, 2024

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jfischer-no commented Sep 5, 2024

Uh oh!

rgrr commented Sep 6, 2024

Uh oh!

josuah commented Oct 23, 2024

Uh oh!

rgrr commented Oct 24, 2024

Uh oh!

josuah commented Oct 24, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

rgrr commented May 4, 2024 •

edited

Loading

josuah commented Oct 24, 2024 •

edited

Loading