On Fri, Jul 26, 2024 at 02:17:00PM -0500, David Lechner wrote: > On 7/26/24 7:38 AM, Rob Herring wrote: > > On Mon, Jul 22, 2024 at 04:57:12PM -0500, David Lechner wrote: > >> The AXI SPI Engine has support for hardware offloading capabilities. > >> There can be up to 32 offload instances per SPI controller, so the > >> bindings limit the value accordingly. > >> > >> Signed-off-by: David Lechner <dlechner@xxxxxxxxxxxx> > >> --- > >> > >> RFC: I have a few questions about this one... > >> > >> 1. The trigger-source properties are borrowed from the leds bindings. > >> Do we want to promote this to a generic binding that can be used by > >> any type of device? > > > > I would make it specific to spi-offload. > > OK > > Meanwhile, we are working on some other ADCs (without SPI offload) and > finding that they are using basically the same sorts of triggers. And > on the driver side of things in this series, I'm getting feedback that > we should have some sort of generic trigger device rather than using, > e.g. a clk directly. If we need this same sort of trigger abstraction > for both SPI offloads and IIO device, it does seems like we might want > to consider something like a new trigger subsystem. A "device" in the sense that "pwm-clk" is a device I suppose. Are any of these other things WIP on the lists (that I may have missed while I was away) or are they still something you're working on internally.
Attachment:
signature.asc
Description: PGP signature