On 10/25/24 5:14 PM, Miquel Raynal wrote: > Every ->exec_op() call correctly configures the spi bus speed to the > maximum allowed frequency for the memory using the constant spi default > parameter. Since we can now have per-operation constraints, let's use > the value that comes from the spi-mem operation structure instead. In > case there is no specific limitation for this operation, the default spi > device value will be given anyway. > > The per-operation frequency capability is thus advertised to the spi-mem > core. > > Signed-off-by: Miquel Raynal <miquel.raynal@xxxxxxxxxxx> > --- > drivers/spi/spi-amlogic-spifc-a1.c | 7 ++++++- > 1 file changed, 6 insertions(+), 1 deletion(-) > > diff --git a/drivers/spi/spi-amlogic-spifc-a1.c b/drivers/spi/spi-amlogic-spifc-a1.c > index fadf6667cd51..18c9aa2cbc29 100644 > --- a/drivers/spi/spi-amlogic-spifc-a1.c > +++ b/drivers/spi/spi-amlogic-spifc-a1.c > @@ -259,7 +259,7 @@ static int amlogic_spifc_a1_exec_op(struct spi_mem *mem, > size_t data_size = op->data.nbytes; > int ret; > > - ret = amlogic_spifc_a1_set_freq(spifc, mem->spi->max_speed_hz); > + ret = amlogic_spifc_a1_set_freq(spifc, op->max_freq); > if (ret) > return ret; > > @@ -320,6 +320,10 @@ static const struct spi_controller_mem_ops amlogic_spifc_a1_mem_ops = { > .adjust_op_size = amlogic_spifc_a1_adjust_op_size, > }; I see the driver sets ctrl->min_speed_hz = SPIFC_A1_MIN_HZ; Do you want to introduce a struct spi_controller_mem_ops.supports_op and check that the spimem op freq is not below the controller's minimum freq?