-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
drivers/can: fix doxygen documentation + typo #7289
Conversation
cpu/native/can/candev_linux.c
Outdated
@@ -7,7 +7,7 @@ | |||
*/ | |||
|
|||
/** | |||
* @ingroup native_cpu | |||
* @ingroup candev_linux |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure about this name... And technically it is in both, so I would keep the removed line.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If one keeps the two, it results in a very weird rendering of the parent groups breadcrumbs. I think removing is one of the best solution.
Maybe I can add a ref to native_cpu: @see native_cpu
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
C-files aren't rendered by our doxygen-config anyways (so there are no breadcrumbs), and @smlng made a move to do that grouping for C-files.
cpu/native/include/candev_linux.h
Outdated
@@ -7,9 +7,9 @@ | |||
*/ | |||
|
|||
/** | |||
* @ingroup native_cpu | |||
* @ingroup drivers_can | |||
* @defgroup candev_linux SocketCAN driver |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about drivers_candev_linux
instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
makes sense
drivers/doc.txt
Outdated
/** | ||
* @defgroup drivers_can CAN Drivers | ||
* @ingroup drivers | ||
* @ingroup can |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(don't know where this is defined, but) we don't have a directory can
in RIOTBASE, so NACK for the name alone. Second, why do we need it? Third, why ist there a whole subgroup under drivers, just for CAN alone?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because CAN is also a separate stack. This group is defined in sys/include/can/doc.txt
. There other opened PR (I 3 or 4) that will provide CAN hardware driver. I was unsure if it should go in the netdev_drivers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LoRa is a seperate stack, too. This doesn't imply that it needs a whole new group. If can
devices don't fit into drivers_netdev
for some reason (because CAN isn't networking (?)) how about renaming it to something like "communication devices"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
renaming it to something like "communication devices"
Do you mean renaming "Network Device Drivers" (drivers_netdev) to "Communication Device Drivers" (drivers_communication) ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but I don't get, why we can't keep the name, just because CAN doesn't use the netdev API... After all, CAN stands for Controller Area Network ;)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For simplicity, we can keep drivers_netdev, but the displayed name can become "Communication Device Drivers".
After all, CAN stands for Controller Area Network ;)
Sure!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I even would keep the displayed name...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TBH I don't even know, why it has its own API... Looking at the API, all of that could have been done with netdev
...
sys/include/can/can.h
Outdated
@@ -7,16 +7,14 @@ | |||
*/ | |||
|
|||
/** | |||
* @ingroup can | |||
* @defgroup can_dll Data Link Layer |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sys_can
sys/include/can/can.h
Outdated
* @defgroup can_dll Data Link Layer | ||
* @ingroup can |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sys
sys/include/can/common.h
Outdated
* @defgroup can_common Common | ||
* @ingroup can |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sys_can
sys/include/can/common.h
Outdated
@@ -7,8 +7,8 @@ | |||
*/ | |||
|
|||
/** | |||
* @ingroup can | |||
* @defgroup can_common Common |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sys_can_common
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Names should adhere to the doc group naming scheme and this PR doesn't fix the grouping IMHO.
sys/include/can/isotp.h
Outdated
@@ -7,12 +7,11 @@ | |||
*/ | |||
|
|||
/** | |||
* @defgroup can_isotp ISOTP |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sys_can_isotp
For the moment, I'll update it so that it does |
@miri64, comments addressed:
I removed the multi-parent grouping because of the bad breadcumbs rendering and put |
* @defgroup drivers_can CAN Drivers | ||
* @ingroup drivers_netdev | ||
* @brief Drivers for CAN devices | ||
* @see sys_can |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add a @note These devices are not covered by the @ref drivers_netdev_api
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and add but by the @ref drivers_candev "candev API"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@miri64, comments addressed.
sys/include/can/isotp.h
Outdated
@@ -7,12 +7,11 @@ | |||
*/ | |||
|
|||
/** | |||
* @ingroup can | |||
* @defgroup isotp ISOTP | |||
* @defgroup sys_can_isotp ISOTP |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please pull up the wording from the brief up here (without the ISO number), but leave the @brief
as is? ISOTP isn't really saying anything to me ;-).
@miri64, are you ok with this one ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apart from some nitpicks: ACK. Please squash
sys/include/can/conn/raw.h
Outdated
@@ -7,15 +7,14 @@ | |||
*/ | |||
|
|||
/** | |||
* @ingroup can | |||
* @defgroup conn_can Connection | |||
* @defgroup sys_conn_can Connection |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nitpicky: sys_can_conn
drivers/can_trx/can_trx.c
Outdated
@@ -7,16 +7,15 @@ | |||
*/ | |||
|
|||
/** | |||
* @defgroup drivers_can transceiver | |||
* @ingroup drivers | |||
* @ingroup drivers_trx_can |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nitpicky: sys_can_trx
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess you mean drivers_can_trx
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes :-)
sys/include/can/isotp.h
Outdated
@@ -7,12 +7,11 @@ | |||
*/ | |||
|
|||
/** | |||
* @ingroup can | |||
* @defgroup isotp ISOTP | |||
* @defgroup sys_can_isotp ISO transport protocol over CAN (ISO15765) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the ISO number can be removed here.
@miri64, remaining nits addressed, directly squashed. |
I found some problems in the CAN doxygen documentation:
This PR solves the 2.