From: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>
To: Patrick Havelange <patrick.havelange@essensium.com>
Cc: Chuhong Yuan <hslester96@gmail.com>,
William Breathitt Gray <vilhelm.gray@gmail.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] counter/ftm-quaddec: Use device-managed registration API
Date: Sat, 27 Jul 2019 14:31:33 +0100 [thread overview]
Message-ID: <20190727143133.26a36f70@archlinux> (raw)
In-Reply-To: <CAKKE0ZG9hKqOnPHCfmW8Mpe2tdcdpdv4Njvx7XNuw6ykJf3P0w@mail.gmail.com>
On Fri, 26 Jul 2019 14:51:30 +0200
Patrick Havelange <patrick.havelange@essensium.com> wrote:
> Hello,
>
> On Fri, Jul 26, 2019 at 4:28 AM Chuhong Yuan <hslester96@gmail.com> wrote:
> >
> > Make use of devm_counter_register.
> > Then we can remove redundant unregistration API
> > usage to make code simpler.
> >
> > Signed-off-by: Chuhong Yuan <hslester96@gmail.com>
> > ---
> > Changes in v2:
> > - Use devm_add_action_or_reset to keep
> > resource release order.
>
> This is better now indeed.
>
> However it seems there is an issue with the mail/patch format, I'm
> unable to apply it with git am, and if you look at
> https://lore.kernel.org/patchwork/patch/1105782/ the diff section is
> missing the beginning of the patch. I don't know why, but I think it
> should be looked into.
>
> Otherwise, it's fine by me.
Hi Patrick,
A formal, Acked-by or Reviewed-by definitely preferred if you are happy
to give one.
This looks fine to me as well. William, if you are happy with the resend
of this, then let me know if you want me to queue it up.
Thanks,
Jonathan
>
> Regards,
>
> Patrick Havelange
>
>
> > - _remove() function is redundant now,
> > delete it.
> >
> > drivers/counter/ftm-quaddec.c | 31 +++++++++++--------------------
> > 1 file changed, 11 insertions(+), 20 deletions(-)
> >
> > diff --git a/drivers/counter/ftm-quaddec.c b/drivers/counter/ftm-quaddec.c
> > index 68a9b7393457..76c70a6c3593 100644
> > --- a/drivers/counter/ftm-quaddec.c
> > +++ b/drivers/counter/ftm-quaddec.c
> > @@ -100,16 +100,17 @@ static void ftm_quaddec_init(struct ftm_quaddec *ftm)
> > ftm_set_write_protection(ftm);
> > }
> >
> > -static void ftm_quaddec_disable(struct ftm_quaddec *ftm)
> > +static void ftm_quaddec_disable(void *ftm)
> > {
> > - ftm_clear_write_protection(ftm);
> > - ftm_write(ftm, FTM_MODE, 0);
> > - ftm_write(ftm, FTM_QDCTRL, 0);
> > + struct ftm_quaddec *ftm_qua = ftm;
> >
> > + ftm_clear_write_protection(ftm_qua);
> > + ftm_write(ftm_qua, FTM_MODE, 0);
> > + ftm_write(ftm_qua, FTM_QDCTRL, 0);
> > /*
> > * This is enough to disable the counter. No clock has been
> > * selected by writing to FTM_SC in init()
> > */
> > - ftm_set_write_protection(ftm);
> > + ftm_set_write_protection(ftm_qua);
> > }
> >
> > static int ftm_quaddec_get_prescaler(struct counter_device *counter,
> > @@ -316,22 +317,13 @@ static int ftm_quaddec_probe(struct platform_device *pdev)
> > mutex_init(&ftm->ftm_quaddec_mutex);
> >
> > ftm_quaddec_init(ftm);
> > -
> > - ret = counter_register(&ftm->counter);
> > + ret = devm_add_action_or_reset(&pdev->dev, ftm_quaddec_disable, ftm);
> > if (ret)
> > - ftm_quaddec_disable(ftm);
> > -
> > - return ret;
> > -}
> > -
> > -static int ftm_quaddec_remove(struct platform_device *pdev)
> > -{
> > - struct ftm_quaddec *ftm = platform_get_drvdata(pdev);
> > -
> > - counter_unregister(&ftm->counter);
> > -
> > - ftm_quaddec_disable(ftm);
> > + return ret;
> >
> > + ret = devm_counter_register(&pdev->dev, &ftm->counter);
> > + if (ret)
> > + return ret;
> > return 0;
> > }
> >
> > @@ -346,7 +338,6 @@ static struct platform_driver ftm_quaddec_driver = {
> > .of_match_table = ftm_quaddec_match,
> > },
> > .probe = ftm_quaddec_probe,
> > - .remove = ftm_quaddec_remove,
> > };
> >
> > module_platform_driver(ftm_quaddec_driver);
> > --
> > 2.20.1
> >
next prev parent reply other threads:[~2019-07-27 13:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 2:28 [PATCH v2] counter/ftm-quaddec: Use device-managed registration API Chuhong Yuan
2019-07-26 12:51 ` Patrick Havelange
2019-07-26 13:21 ` Chuhong Yuan
2019-07-27 13:31 ` Jonathan Cameron [this message]
2019-07-27 18:13 ` William Breathitt Gray
-- strict thread matches above, loose matches on Subject: below --
2019-07-26 13:39 Chuhong Yuan
2019-07-27 21:27 ` Jonathan Cameron
2019-07-29 11:52 ` Patrick Havelange
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=20190727143133.26a36f70@archlinux \
--to=jic23@jic23.retrosnub.co.uk \
--cc=hslester96@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick.havelange@essensium.com \
--cc=vilhelm.gray@gmail.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;
as well as URLs for NNTP newsgroup(s).