From: Alex Tran <alex.tran@oss.qualcomm.com>
To: Bartosz Golaszewski <brgl@kernel.org>,
Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: Linus Walleij <linusw@kernel.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Dan Carpenter <error27@gmail.com>,
AKASHI Takahiro <takahiro.akashi@linaro.org>,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Subject: Re: [PATCH v2] gpio: gpio-by-pinctrl: Apply initial value in direction output wrapper
Date: Mon, 10 Aug 2026 10:31:12 -0700 [thread overview]
Message-ID: <845345b5-bdc2-4f3a-91c1-b457059ed063@oss.qualcomm.com> (raw)
In-Reply-To: <CAMRc=MeLUhxzbQuVONj4dESPD98Sx-+yx7jjuNpovLaPazyj=g@mail.gmail.com>
On 8/10/2026 3:41 AM, Bartosz Golaszewski wrote:
> On Thu, 6 Aug 2026 23:59:26 +0200, Andy Shevchenko
> <andriy.shevchenko@intel.com> said:
>> On Mon, Jul 27, 2026 at 01:14:40PM +0200, Bartosz Golaszewski wrote:
>>> On Fri, 24 Jul 2026 09:42:28 -0700, Alex Tran wrote:
>>>> After successfully configuring gpio pin as output, set the
>>>> requested initial output value via the existing gpio set
>>>> wrapper, so that the pin is not left at its previous level.
>>> Applied, thanks!
>>>
>>> [1/1] gpio: gpio-by-pinctrl: Apply initial value in direction output wrapper
>>> https://git.kernel.org/brgl/c/67ff4bf723c8bd1f1b10450fa3e8f55762418104
>> Thanks, but see my comment.
>>
>> --
>> With Best Regards,
>> Andy Shevchenko
>>
>>
>>
> Sorry, I was on vacation. Alex: can you please look into Andy's comment?
>
> Thanks,
> Bartosz
Sure, I'll address the ordering issue Andy raised.
Alex
next prev parent reply other threads:[~2026-08-10 17:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 16:42 Alex Tran
2026-07-25 14:01 ` Linus Walleij
2026-07-27 11:14 ` Bartosz Golaszewski
2026-08-06 21:59 ` Andy Shevchenko
2026-08-10 10:41 ` Bartosz Golaszewski
2026-08-10 17:31 ` Alex Tran [this message]
2026-08-06 21:58 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=845345b5-bdc2-4f3a-91c1-b457059ed063@oss.qualcomm.com \
--to=alex.tran@oss.qualcomm.com \
--cc=andriy.shevchenko@intel.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=error27@gmail.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=takahiro.akashi@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®