From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Walleij Subject: Re: [PATCH 3/4] bcm2835-gpio-exp: Driver for GPIO expander via mailbox service Date: Wed, 3 Jan 2018 11:08:15 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: Sender: linux-gpio-owner@vger.kernel.org To: Baruch Siach Cc: Dave Stevenson , Eric Anholt , Stefan Wahren , linux-gpio@vger.kernel.org, Linux ARM , linux-rpi-kernel , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" List-Id: devicetree@vger.kernel.org On Tue, Jan 2, 2018 at 2:19 PM, Baruch Siach wrote: > +config GPIO_BCM_EXP > + bool "Broadcom Exp GPIO" > + depends on OF_GPIO && RASPBERRYPI_FIRMWARE && (ARCH_BCM2835 || COMPILE_TEST) > + help > + Turn on GPIO support for Broadcom chips using the firmware mailbox > + to communicate with VideoCore on BCM283x chips. Should this be default RASPBERRYPI_FIRMWARE So it is always available if the firmware interface is there? > +#include > +#include Just use #include > +#define MODULE_NAME "brcmexp-gpio" > +#define NUM_GPIO 8 > + > +struct brcmexp_gpio { > + struct gpio_chip gc; > + struct device *dev; > + struct rpi_firmware *fw; > +}; > + > +struct gpio_set_config { > + u32 gpio, direction, polarity, term_en, term_pull_up, state; > +}; > + > +struct gpio_get_config { > + u32 gpio, direction, polarity, term_en, term_pull_up; > +}; Seems to support some pin control stuff, hm? The pull ups seems unused though so OK. Yours, Linus Walleij