[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3c5b6ae1-387f-143c-691f-92b96fe78270@linaro.org>
Date: Sun, 29 Jan 2023 17:01:32 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: nl250060@....com, Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <brgl@...ev.pl>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>
Cc: linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] gpio: mmio: Use new flag BGPIOF_NO_INPUT
On 26/01/2023 11:17, Niall Leonard via B4 Submission Endpoint wrote:
> From: Niall Leonard <nl250060@....com>
>
> Use the existing shadow data register 'bgpio_data' to allow
> the last written value to be returned by the read operation
> when BGPIOF_NO_INPUT flag is set.
>
(...)
> if (gc->set == bgpio_set_set &&
> !(flags & BGPIOF_UNREADABLE_REG_SET))
> gc->bgpio_data = gc->read_reg(gc->reg_set);
> @@ -711,6 +723,9 @@ static struct bgpio_pdata *bgpio_parse_dt(struct platform_device *pdev,
> if (of_property_read_bool(pdev->dev.of_node, "no-output"))
> *flags |= BGPIOF_NO_OUTPUT;
>
> + if (of_property_read_bool(pdev->dev.of_node, "no-input"))
As pointed, this brings undocumented property to two other bindings.
This needs to be fixed.
Best regards,
Krzysztof
Powered by blists - more mailing lists