Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

SPI: cs_change not working properly

Open
#85 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
c

Research direction

Start in drivers/spi/spi-omap2-mcspi.c at omap2_mcspi_work(), then trace how the t->cs_change branch controls omap2_mcspi_force_cs() and transaction state. Compare that behavior with the stated SPI contract for keeping chip select active after the function returns. Done means cs_change preserves the active chip select as requested without breaking the final transfer handling.

Written by the indexing model from the issue text.

Description

In file drivers/spi/spi-omap2-mcspi.c funcion omap2_mcspi_work()

/* ignore the "leave it on after last xfer" hint */
if (t->cs_change) {
    omap2_mcspi_force_cs(spi, 0);
    cs_active = 0;
}

Setting cs_change is supposed to keep the chip select pin active after returning from the function.
This code does not allow to keep the transaction alive.

Dominant language
Shell
Stars
172
Forks
156
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from beagleboard/kernel

All issues in beagleboard/kernel

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.