New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 611549 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature

Blocked on:
issue chrome-os-partner:20257

Blocking:
issue 807504



Sign in to add a comment

ec: keep only v3 support for new board

Project Member Reported by gwendal@chromium.org, May 12 2016

Issue description

Since kernel v3.14, we support protocol v3 in the kernel. (chrome-os-partner:20257)
Therefore, for newer board or newer firmware revision where we are sure the AP is using v3.14 or later, we can remove v2 support.

stm32 i2c already only support v3.
stm32 spi still support v2 if CONFIG_SPI_PROTOCOL_V2 is compiled in.
xxx lpc still support v2,

Still, even when only v3 is supported, we are rather inefficient: We translate the "v3 message" (packet) into a "v2 message" (command) and calling the older style command processing function: host_command_received()

We should be able to squeeze some flash and cycle there.
 
Blockedon: chrome-os-partner:20257
Summary: ec: keep only v3 support for new board (was: ec: keep on v3 support for new board)
Owner: sha...@chromium.org
Status: Assigned (was: Untriaged)
Is there more to be done here?
Yes, we can remove CONFIG_SPI_PROTOCOL_V2 and prevent a translation.
Blocking: 807504

Sign in to add a comment