robertlipe commented on issue #5810: URL: https://github.com/apache/incubator-nuttx/issues/5810#issuecomment-1076989863
I saw that in ESP32C3-C3. That's how I knew it was the only other board to support as many as TWO GPIO pins - they do that very kconfig/add the #if defined thing that I suggested in one option in one of my patches. But there are a dozen other GPIOs on the chip. ioctl gives up any real type checking. You're not going to manipulate pins via 'echo' from user mode that way, for example. That should be a last call, IMO. ESP's code is coming beneath the standard GPIO layer. There should probably be a generic LCD driver that knows how to do open /dev/gpiio* and do reads and writes on the appropriate GPIO pins ot flip DC and Backlight as that's such a common thing. That basic ESP32 driver would be the right shapce, but it "just" needs to open /dev/gpio*whatever* and issues writes to /dev/gpio whatever instead of directly calling across kernel modules like that. On Wed, Mar 23, 2022 at 6:36 PM Lee Lup Yuen ***@***.***> wrote: > Or we can implement a I/O Expander Driver for BL602, if we prefer to > manipulate BL602 GPIOs directly from our NuttX App... > > > https://github.com/apache/incubator-nuttx/blob/master/drivers/ioexpander/ioe_dummy.c > > — > Reply to this email directly, view it on GitHub > <https://github.com/apache/incubator-nuttx/issues/5810#issuecomment-1076920169>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACCSD34GAIHZG5F4OW5BOK3VBOTHRANCNFSM5RGMP4IQ> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
