From: hzpeterchen@gmail.com (Peter Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/6] power: add power sequence library
Date: Thu, 4 Aug 2016 14:04:57 +0800 [thread overview]
Message-ID: <20160804060457.GA27272@shlinux2> (raw)
In-Reply-To: <20160803221658.GD1405@google.com>
On Wed, Aug 03, 2016 at 03:16:58PM -0700, Matthias Kaehlcke wrote:
> El Tue, Aug 02, 2016 at 11:30:48AM +0800 Peter Chen ha dit:
>
> > diff --git a/drivers/power/pwrseq/core.c b/drivers/power/pwrseq/core.c
> >
> > ...
> >
> > +static DEFINE_MUTEX(pwrseq_list_mutex);
> > +static LIST_HEAD(pwrseq_list);
> > +
> > +int pwrseq_get(struct device_node *np, struct pwrseq *p)
> > +{
> > + if (p && p->get)
> > + return p->get(np, p);
> > +
> > + return -ENOTSUPP;
> > +}
> > +
> > +int pwrseq_on(struct device_node *np, struct pwrseq *p)
> > +{
> > + if (p && p->on)
> > + return p->on(np, p);
> > +
> > + return -ENOTSUPP;
> > +}
> > +
> > +void pwrseq_off(struct pwrseq *p)
> > +{
> > + if (p && p->off)
> > + p->off(p);
> > +}
> > +
> > +void pwrseq_put(struct pwrseq *p)
> > +{
> > + if (p && p->put)
> > + p->put(p);
> > +}
> > +
> > +void pwrseq_free(struct pwrseq *p)
> > +{
> > + if (p && p->free)
> > + p->free(p);
> > +}
> > +
> > +void pwrseq_register(struct pwrseq *pwrseq)
> > +{
> > + mutex_lock(&pwrseq_list_mutex);
> > + list_add(&pwrseq->node, &pwrseq_list);
> > + mutex_unlock(&pwrseq_list_mutex);
> > +}
> > +
> > +void pwrseq_unregister(struct pwrseq *pwrseq)
> > +{
> > + mutex_lock(&pwrseq_list_mutex);
> > + list_del(&pwrseq->node);
> > + mutex_unlock(&pwrseq_list_mutex);
> > +}
>
> What is the purpose of pwrseq_register/unregister()? The pwrseq
> structs are added and removed from pwrseq_list, but besides that
> pwrseq_list is not used.
>
I had thought we may need to dump the pwrseq list in future for debug
purpose. I will delete this unnecessary code.
--
Best Regards,
Peter Chen
next prev parent reply other threads:[~2016-08-04 6:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 3:30 [PATCH v4 0/6] power: add power sequence library Peter Chen
2016-08-02 3:30 ` [PATCH v4 1/6] binding-doc: power: pwrseq-generic: add binding doc for generic " Peter Chen
2016-08-02 3:30 ` [PATCH v4 2/6] power: add " Peter Chen
2016-08-03 22:16 ` Matthias Kaehlcke
2016-08-04 6:04 ` Peter Chen [this message]
2016-08-02 3:30 ` [PATCH v4 3/6] binding-doc: usb: usb-device: add optional properties for power sequence Peter Chen
2016-08-02 3:30 ` [PATCH v4 4/6] usb: core: add power sequence handling for USB devices Peter Chen
2016-08-02 3:30 ` [PATCH v4 5/6] usb: chipidea: let chipidea core device of_node equal's glue layer device of_node Peter Chen
2016-08-02 3:30 ` [PATCH v4 6/6] ARM: dts: imx6qdl-udoo.dtsi: fix onboard USB HUB property Peter Chen
2016-08-06 12:00 ` [PATCH v4 0/6] power: add power sequence library Oscar
2016-08-08 1:57 ` Peter Chen
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=20160804060457.GA27272@shlinux2 \
--to=hzpeterchen@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).