On Fri, Nov 17, 2023 at 08:10:53PM +0530, Raag Jadav wrote: > Instead of comparing parameters for every supported mem_ops, only compare > on opcode match, which is relatively more efficient. > > Signed-off-by: Raag Jadav <raag.jadav@xxxxxxxxx> Reviewed-by: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx>
Re: [PATCH v1] spi: intel: make mem_ops comparison unique to opcode match
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH v1] spi: intel: make mem_ops comparison unique to opcode match
- From: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx>
- Date: Sat, 18 Nov 2023 08:30:10 +0200
- Cc: broonie@xxxxxxxxxx, andriy.shevchenko@xxxxxxxxxxxxxxx, linux-spi@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
- In-reply-to: <20231117144053.24005-1-raag.jadav@intel.com>
- References: <20231117144053.24005-1-raag.jadav@intel.com>
- References:
- Prev by Date: Re: [PATCH 09/14] spi: axi-spi-engine: move msg state to new struct
- Next by Date: [PATCH -next 04/14] kddv/core: Check kmsg before return from test case
- Previous by thread: [PATCH v1] spi: intel: make mem_ops comparison unique to opcode match
- Next by thread: Re: [PATCH v1] spi: intel: make mem_ops comparison unique to opcode match
- Index(es):
 |