public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@oss.nxp.com>
To: Michal Simek <michal.simek@amd.com>, Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de, git@amd.com,
	Arturs Artamonovs <arturs.artamonovs@analog.com>,
	Eoin Dickson <eoin.dickson@microchip.com>,
	Greg Malysa <malysagreg@gmail.com>,
	Ian Roberts <ian.roberts@timesys.com>,
	Nathan Barrett-Morrison <nathan.morrison@timesys.com>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Oliver Gaskell <Oliver.Gaskell@analog.com>,
	Rasmus Villemoes <ravi@prevas.dk>,
	Tanmay Kathpalia <tanmay.kathpalia@altera.com>,
	Tom Rini <trini@konsulko.com>,
	Utsav Agarwal <utsav.agarwal@analog.com>,
	Vasileios Bimpikas <vasileios.bimpikas@analog.com>,
	Yegor Yefremov <yegorslists@googlemail.com>
Subject: Re: [PATCH 1/3] gpio: Add GPIO delay driver
Date: Tue, 3 Feb 2026 09:36:19 +0800	[thread overview]
Message-ID: <aYFRE69oIA9Dk1WH@nxa18884-linux.ap.freescale.net> (raw)
In-Reply-To: <de5823b9-2214-47ae-9b4c-77cd413e34f1@amd.com>

Hi Michal,

On Fri, Jan 30, 2026 at 09:29:49AM +0100, Michal Simek wrote:
>
>
>> 
>> Add an entry for SPL?
>
>Why? I don't have a need for it and someone should test it if this should be
>used in SPL. That can be done on the top of this when tested.

I see. 

>
>
>> > #
>> > + * Copyright (C) 2025 - 2026, Advanced Micro Devices, Inc.
>> 
>> Drop 2025?
>
>Why? Driver was developed in 2025 but upstreaming happens in 2026.

I think the year should start from the day of upstreaming. Not sure.
Tom may comment.

>
>> 
>> > + *
>> > +
>> > +	/* Request all GPIOs described in the controller node */
>> > +	for (i = 0; i < ngpio; i++) {
>> > +		d = &priv->descs[i];
>> > +		ret = gpio_request_by_name_nodev(node, "gpios", i,
>> > +						 &d->real_gpio, GPIOD_IS_OUT);
>> 
>> This will configure the GPIO as output and ACTIVE high/low flag will also
>> be used per my understanding.
>> 
>> Should the dir and value be deferred until set_value is invoked?
>
>It is clear that it should be output because you just setting it up later.
>But I don't have any issue not to pass any flag here.
>Please let me know if you want me to change it to 0.

Yes, please. Configure it only when user request.

Thanks,
Peng

>
>Thanks,
>Michal
>
>

  reply	other threads:[~2026-02-03  0:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-22 12:50 [PATCH 0/3] gpio: Introduce gpio-delay driver and enable it on Kria Michal Simek
2026-01-22 12:50 ` [PATCH 1/3] gpio: Add GPIO delay driver Michal Simek
2026-01-30  7:21   ` Peng Fan
2026-01-30  8:29     ` Michal Simek
2026-02-03  1:36       ` Peng Fan [this message]
2026-02-03  1:06         ` Tom Rini
2026-02-03  7:02           ` Michal Simek
2026-01-22 12:50 ` [PATCH 2/3] xilinx: Enable GPIO delay driver on Kria platforms Michal Simek
2026-01-22 12:50 ` [PATCH 3/3] arm64: zynqmp: Wire gpio-delay driver for USB hub reset Michal Simek
2026-01-28  6:00   ` Pandey, Radhey Shyam

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=aYFRE69oIA9Dk1WH@nxa18884-linux.ap.freescale.net \
    --to=peng.fan@oss.nxp.com \
    --cc=Oliver.Gaskell@analog.com \
    --cc=arturs.artamonovs@analog.com \
    --cc=eoin.dickson@microchip.com \
    --cc=git@amd.com \
    --cc=ian.roberts@timesys.com \
    --cc=malysagreg@gmail.com \
    --cc=michal.simek@amd.com \
    --cc=nathan.morrison@timesys.com \
    --cc=neil.armstrong@linaro.org \
    --cc=ravi@prevas.dk \
    --cc=tanmay.kathpalia@altera.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=utsav.agarwal@analog.com \
    --cc=vasileios.bimpikas@analog.com \
    --cc=yegorslists@googlemail.com \
    /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