On Thu, 2019-10-24 at 19:01 +0300, Andriy Gapon wrote:
> Also, if we universally implement GPIO_PIN_PRESET we still need to answer the
> question. Because some consumer might still try to change an input, either by
> mistake or for some reason, and we need a rule on how to handle that.
Well, yeah
On 24/10/2019 18:38, Ian Lepore wrote:
> On Thu, 2019-10-24 at 17:04 +0300, Andriy Gapon wrote:
>> For a lack of a more specific mailing list (or my not being aware of it),
>> asking
>> here.
>>
>> gpioiic, a very simple driver, has this code:
>> ===
On Thu, 2019-10-24 at 17:04 +0300, Andriy Gapon wrote:
> For a lack of a more specific mailing list (or my not being aware of it),
> asking
> here.
>
> gpioiic, a very simple driver, has this code:
> ===
> static void
> gpioi
For a lack of a more specific mailing list (or my not being aware of it), asking
here.
gpioiic, a very simple driver, has this code:
===
static void
gpioiic_setsda(device_t dev, int val)
{
struct gpioiic_softc
