linux-toradex.git/drivers/net/ipa/ipa_endpoint.c, branch v5.14

net: ipa: FLAVOR_0 register doesn't exist until IPA v3.5

2021-06-21T19:30:59+00:00

The FLAVOR_0 version first appears in IPA v3.5, so avoid attempting
to read it for versions prior to that.

This register contains a concise definition of the number and
direction of endpoints supported by the hardware, and without it
we can't verify endpoint configuration in ipa_endpoint_config().
In this case, just indicate that any endpoint number is available
for use.

Originally proposed by AngeloGioacchino Del Regno.

Link: https://lore.kernel.org/netdev/20210211175015.200772-3-angelogioacchino.delregno@somainline.org
Signed-off-by: Alex Elder 
Acked-by: AngeloGioacchino Del Regno
Signed-off-by: David S. Miller

net: ipa: make endpoint data validation unconditional

2021-06-11T21:13:18+00:00

The cost of validating the endpoint configuration data is not all
that high, so just do it unconditionally, rather than doing so only
when IPA_VALIDATAION is defined.

Suggested-by: Leon Romanovsky 
Signed-off-by: Alex Elder 
Signed-off-by: David S. Miller

Revert "net: ipa: disable checksum offload for IPA v4.5+"

2021-06-03T22:09:40+00:00

This reverts commit c88c34fcf8f501d588c0a999aa7e51e18552c5f0.

The RMNet driver now supports inline checksum offload.

Signed-off-by: Alex Elder 
Signed-off-by: David S. Miller

net: ipa: add support for inline checksum offload

2021-06-03T22:09:40+00:00

Starting with IPA v4.5, IP payload checksum offload is implemented
differently.

Prior to v4.5, the IPA hardware appends an rmnet_map_dl_csum_trailer
structure to each packet if checksum offload is enabled in the
download direction (modem->AP).  In the upload direction (AP->modem)
a rmnet_map_ul_csum_header structure is prepended before each sent
packet.

Starting with IPA v4.5, checksum offload is implemented using a
single new rmnet_map_v5_csum_header structure which sits between
the QMAP header and the packet data.  The same header structure
is used in both directions.

The new header contains a header type (CSUM_OFFLOAD); a checksum
flag; and a flag indicating whether any other headers follow this
one.  The checksum flag indicates whether the hardware should
compute (and insert) the checksum on a sent packet.  On a received
packet the checksum flag indicates whether the hardware confirms the
checksum value in the payload is correct.

Signed-off-by: Alex Elder 
Signed-off-by: David S. Miller

net: ipa: disable checksum offload for IPA v4.5+

2021-04-11T23:49:08+00:00

Checksum offload for IPA v4.5+ is implemented differently, using
"inline" offload (which uses a common header format for both upload
and download offload).

The IPA hardware must be programmed to enable MAP checksum offload,
but the RMNet driver is responsible for interpreting checksum
metadata supplied with messages.

Currently, the RMNet driver does not support inline checksum offload.
This support is imminent, but until it is available, do not allow
newer versions of IPA to specify checksum offload for endpoints.

Signed-off-by: Alex Elder 
Signed-off-by: David S. Miller

net: ipa: three small fixes

2021-04-10T03:57:26+00:00

Some time ago changes were made to stop referring to clearing the
hardware pipeline as a "tag process."  Fix a comment to use the
newer terminology.

Get rid of a pointless double-negation of the Boolean toward_ipa
flag in ipa_endpoint_config().

make ipa_endpoint_exit_one() private; it's only referenced inside
"ipa_endpoint.c".

Signed-off-by: Alex Elder 
Signed-off-by: Jakub Kicinski

net: ipa: remove repeated words

2021-03-30T23:56:39+00:00

Remove repeated words "that" and "the".

Signed-off-by: Peng Li 
Signed-off-by: Huazhong Tan 
Acked-by: Alex Elder 
Signed-off-by: David S. Miller

net: ipa: define the ENDP_INIT_NAT register

2021-03-24T23:52:47+00:00

Define the ENDP_INIT_NAT register for setting up the NAT
configuration for an endpoint.  We aren't using NAT at this
time, so explicitly set the type to BYPASS for all endpoints.

Signed-off-by: Alex Elder 
Signed-off-by: David S. Miller

net: ipa: reduce IPA version assumptions

2021-03-24T23:52:47+00:00

Modify conditional tests throughout the IPA code so they do not
assume that IPA v3.5.1 is the oldest version supported.  Also remove
assumptions that IPA v4.5 is the newest version of IPA supported.

Augment versions in comments with "+", to be clearer that the
comment applies to a version and subsequent versions.  (E.g.,
"present for IPA v4.2+" instead of just "present for v4.2".)

Signed-off-by: Alex Elder 
Signed-off-by: David S. Miller

net: ipa: sequencer type is for TX endpoints only

2021-03-21T01:56:18+00:00

We only program the sequencer type for TX endpoints.  So move the
definition of the sequencer type fields into the TX-specific portion
of the endpoint configuration data.  There's no need to maintain
this in the IPA structure; we can extract it from the configuration
data it points to in the one spot it's needed.

We previously specified the sequencer type for RX endpoints with
INVALID values.  These are no longer needed, so get rid of them.

Signed-off-by: Alex Elder 
Signed-off-by: David S. Miller