From: Fabio Aiuto <fabioaiuto83@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 1/4] fbtft: Replace custom ->reset() with generic one
Date: Sat, 17 Apr 2021 09:18:41 +0200 [thread overview]
Message-ID: <20210417071838.GA1401@agape.jhs> (raw)
In-Reply-To: <20210416142044.17766-1-andriy.shevchenko@linux.intel.com>
Hi,
'staging:' in mail subject is missing...
On Fri, Apr 16, 2021 at 05:20:41PM +0300, Andy Shevchenko wrote:
> The custom ->reset() repeats the generic one, replace it.
>
> Note, in newer kernels the context of the function is a sleeping one,
> it's fine to switch over to the sleeping functions. Keeping the reset
> line asserted longer than 20 microseconds is also okay, it's an idling
> state of the hardware.
>
> Fixes: b2ebd4be6fa1 ("staging: fbtft: add fb_agm1264k-fl driver")
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> v2: new patch split from the bigger fix (Greg)
> drivers/staging/fbtft/fb_agm1264k-fl.c | 14 --------------
> 1 file changed, 14 deletions(-)
>
> diff --git a/drivers/staging/fbtft/fb_agm1264k-fl.c b/drivers/staging/fbtft/fb_agm1264k-fl.c
> index eeeeec97ad27..4dfc22d05a40 100644
> --- a/drivers/staging/fbtft/fb_agm1264k-fl.c
> +++ b/drivers/staging/fbtft/fb_agm1264k-fl.c
> @@ -77,19 +77,6 @@ static int init_display(struct fbtft_par *par)
> return 0;
> }
>
> -static void reset(struct fbtft_par *par)
> -{
> - if (!par->gpio.reset)
> - return;
> -
> - dev_dbg(par->info->device, "%s()\n", __func__);
> -
> - gpiod_set_value(par->gpio.reset, 0);
> - udelay(20);
> - gpiod_set_value(par->gpio.reset, 1);
> - mdelay(120);
> -}
> -
> /* Check if all necessary GPIOS defined */
> static int verify_gpios(struct fbtft_par *par)
> {
> @@ -439,7 +426,6 @@ static struct fbtft_display display = {
> .set_addr_win = set_addr_win,
> .verify_gpios = verify_gpios,
> .request_gpios_match = request_gpios_match,
> - .reset = reset,
> .write = write,
> .write_register = write_reg8_bus8,
> .write_vmem = write_vmem,
> --
> 2.30.2
>
>
thank you,
fabio
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-04-17 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 14:20 [PATCH v2 1/4] fbtft: Replace custom ->reset() with generic one Andy Shevchenko
2021-04-16 14:20 ` [PATCH v2 2/4] fbtft: Rectify GPIO handling Andy Shevchenko
2021-04-16 14:20 ` [PATCH v2 3/4] fbtft: Don't spam logs when probe is deferred Andy Shevchenko
2021-04-16 14:20 ` [PATCH v2 4/4] fbtft: Update TODO Andy Shevchenko
2021-04-17 7:18 ` Fabio Aiuto [this message]
2021-04-27 11:07 ` [PATCH v2 1/4] fbtft: Replace custom ->reset() with generic one Greg Kroah-Hartman
2021-04-27 12:10 ` 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=20210417071838.GA1401@agape.jhs \
--to=fabioaiuto83@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).