From: carlis <zhangxuezhi3@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "open list:STAGING SUBSYSTEM" <devel@driverdev.osuosl.org>,
"open list:FRAMEBUFFER LAYER" <linux-fbdev@vger.kernel.org>,
Deepak R Varma <mh12gx2825@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
oliver.graute@kococonnector.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Stefano Brivio <sbrivio@redhat.com>,
Colin King <colin.king@canonical.com>,
zhangxuezhi1@yulong.com
Subject: Re: [PATCH v12] staging: fbtft: add tearing signal detect
Date: Fri, 29 Jan 2021 20:54:47 +0800 [thread overview]
Message-ID: <20210129205447.0000464f@gmail.com> (raw)
In-Reply-To: <CAHp75Vdi4H_zY3+QPSq_wmdf20B9xPeqsOT10JHfMLJESX77gA@mail.gmail.com>
On Fri, 29 Jan 2021 12:23:08 +0200
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> On Fri, Jan 29, 2021 at 7:01 AM carlis <zhangxuezhi3@gmail.com> wrote:
> > On Thu, 28 Jan 2021 16:33:02 +0200
> > Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> > > On Thu, Jan 28, 2021 at 2:58 PM Carlis <zhangxuezhi3@gmail.com>
> > > wrote:
> > >
> > > Thanks for your contribution, my comments below.
> > >
> > > > From: zhangxuezhi <zhangxuezhi1@yulong.com>
> > >
> > > You probably have to configure your Git to use the same account
> > > for author and committer.
> >
> > hi,you mean like below:
> > Carlis <zhangxuezhi1@yulong.com>
> > ?
>
> I meant that you shouldn't probably have a From: line in the commit
> message.
>
> ...
>
> > hi, i have modified it according to your suggestion like below:
>
> Please, go again thru my comments and comments from others and
> carefully address all of them everywhere in your contribution. If you
> have questions, ask them in reply in the corresponding context.
>
> ...
>
> > /**
> > * init_tearing_effect_line() - init tearing effect line
>
> > *
>
> For example, above was commented on and hasn't been addressed here.
>
> > * @par: FBTFT parameter object
> > *
> > * Return: 0 on success, < 0 if error occurred.
> > */
> > static int init_tearing_effect_line(struct fbtft_par *par)
> > {
> > struct device *dev = par->info->device;
> > struct gpio_desc *te;
> > int rc;
> >
> > te = gpiod_get_optional(dev, "te", GPIOD_IN);
> > if (IS_ERR(te))
> > return dev_err_probe(dev, PTR_ERR(te), "Failed to
> > request te GPIO\n");
> >
>
> > if (te) {
>
> This one is not like I suggested.
I don't think I have a problem here, if te GPIO is not configured, it
should return NULL, if it is configured, it should be greater than 0
>
> > par->irq_te = gpiod_to_irq(te);
> > gpiod_put(te);
> >
>
> > if (par->irq_te) {
>
> This is wrong.
>
> > rc = devm_request_irq(dev,
> > par->irq_te,
> > panel_te_handler,
> > IRQF_TRIGGER_RISING,
> > "TE_GPIO", par);
>
> Try to use less LOCs.
LOCs???? i can not get you
>
> > if (rc)
> > return dev_err_probe(dev, rc, "TE
> > IRQ request failed.\n");
> >
> > disable_irq_nosync(par->irq_te);
> > init_completion(&par->panel_te);
>
> > } else {
> > return dev_err_probe(dev, par->irq_te,
> > "gpiod to TE IRQ failed.\n");
> > }
>
> Again, it is not what had been suggested.
>
> > }
> >
> > return 0;
> > }
>
> The rest is better, but we will see later on when you submit a new
> version (And I feel it won't be last).
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-01-30 11:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 12:53 [PATCH v12] staging: fbtft: add tearing signal detect Carlis
2021-01-28 12:58 ` Greg KH
2021-01-28 14:33 ` Andy Shevchenko
2021-01-28 14:44 ` Andy Shevchenko
2021-01-28 15:23 ` Dan Carpenter
2021-01-29 5:01 ` carlis
2021-01-29 10:23 ` Andy Shevchenko
2021-01-29 10:45 ` Greg Kroah-Hartman
2021-01-29 12:47 ` carlis
2021-01-29 14:01 ` Andy Shevchenko
2021-01-29 12:54 ` carlis [this message]
2021-01-29 14:04 ` Andy Shevchenko
2021-01-29 13:56 ` carlis
2021-01-29 14:26 ` Andy Shevchenko
2021-01-30 6:39 ` carlis
2021-02-01 17:40 ` Andy Shevchenko
2021-02-02 1:52 ` Carlis
2021-02-15 15:30 ` 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=20210129205447.0000464f@gmail.com \
--to=zhangxuezhi3@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=colin.king@canonical.com \
--cc=devel@driverdev.osuosl.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mh12gx2825@gmail.com \
--cc=oliver.graute@kococonnector.com \
--cc=sbrivio@redhat.com \
--cc=zhangxuezhi1@yulong.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