zynq_qspi_config_op(9)

🎀 zynq_qspi_config_op(9) 🎀

okay so bestie, welcome to this page from the Kernel API Manual — it’s giving “tiny function, very specific job,” and honestly? iconic. This one is all about configuring the QSPI controller for a specified transfer. 💅✨

🌸 NAME 🌸

• zynq_qspi_config_op — Configure QSPI controller for specified transfer.

🦋 SYNOPSIS 🦋

int zynq_qspi_config_op (struct zynq_qspi *xqspi , struct spi_device
*spi , const struct spi_mem_op *op );

✨ ARGUMENTS ✨

bestie, here’s the cast of characters you pass in:

• xqspi — Pointer to the zynq_qspi structure.
• spi — Pointer to the spi_device structure.
• op — The memory operation to execute.

💜 DESCRIPTION 💜

This function sets the operational mode of the QSPI controller for the next QSPI transfer, and it sets the requested clock frequency.

That’s the whole main-character job: mode for the next transfer, requested clock frequency, done. periodt. 🔥

🔥 RETURN 🔥

It returns 0 on success and -EINVAL on invalid input parameter.

so if you get -EINVAL, your input parameter said no 💀 — check it, bestie.

🫶 NOTE 🫶

⚠️ frequency behavior is lowkey important, so listen up: If the requested frequency is not an exact match with what can be obtained using the prescalar value, the driver sets the clock frequency which is lower than the requested frequency (maximum lower) for the transfer. If the requested frequency is higher or lower than that is supported by the QSPI controller, the driver will set the highest or lowest frequency supported by controller.

🌈 SEE ALSO 🌈

Kernel file ./drivers/spi/spi-zynq-qspi.c is the home base. The whole squad is: struct zynq_qspi(9), zynq_qspi_init_hw(9), zynq_qspi_rxfifo_op(9), zynq_qspi_txfifo_op(9), zynq_qspi_chipselect(9), zynq_qspi_setup_op(9), zynq_qspi_write_op(9), zynq_qspi_read_op(9), zynq_qspi_irq(9), zynq_qspi_exec_mem_op(9), zynq_qspi_probe(9), zynq_qspi_remove(9).

---

okay bye bestie — source/version info: ./drivers/spi, and this page is dated October 2026 💖🫶💅