On Mon, Jan 6, 2020 at 5:25 PM Jinpu Wang <jinpu.wang@xxxxxxxxxxxxxxx> wrote: > > On Tue, Dec 24, 2019 at 5:41 AM Deepak Ukey <deepak.ukey@xxxxxxxxxxxxx> wrote: > > > > From: Deepak Ukey <Deepak.Ukey@xxxxxxxxxxxxx> > > > > Added IOCTL functionality for GPIO. > > The SPCv controller provides 24 GPIO signals. The first 12 signals > > [11:0] and the last 4 signals [23:20] are for customer use. Eight > > signals [19:12] are reserved for the SPCv controller firmware. > > Whenever the host performs GPIO setup or a read/write operation > > using the GPIO command the host needs to make sure that it does > > not disturb the GPIO configuration for the bits [19:12]. > > Each signal can be configured either as an input or as an output. > > When configured as an output, the host can use the GPIO Command to > > set the desired level. GPIO inputs can also be configured so that > > the SPCv controller sends the GPIO Event notification when specific > > GPIO events occur. > > Different GPIO features implemented: > > 1) GPIO Pin Setup > > 2) GPIO Event Setup > > 3) GPIO Read > > 4) GPIO Write > > > > I think you can also implement lldd_write_gpio callback, so smp_utils > can also control gpio, right? This comment should go to SGPIO, patch09
