From: Sean Cross <xobs-nXMMniAx+RbQT0dZR+AlfA@public.gmane.org>
To: Liam Girdwood <lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Grant Likely
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Sean Cross <xobs-nXMMniAx+RbQT0dZR+AlfA@public.gmane.org>
Subject: [PATCH 0/2] regulator: pfuze100: Minor driver enhancements
Date: Mon, 26 May 2014 16:45:39 +0800 [thread overview]
Message-ID: <1401093941-12386-1-git-send-email-xobs@kosagi.com> (raw)
The PFUZE100 supports enabling/disabling of SWB regulators, but the driver
doesn't currently support this. The first patch adds support for the
enable/disable bit.
Additionally, there is a minor bug wherein GPIO0 IO0 will sometimes get
allocated as the PFUZE100 ena_gpio, due to the fact that ena_gpio defaults
to 0 which is a valid gpio. The second patch fixes this case.
Sean Cross (2):
regulator: pfuze100: Support SWB enable/disable
regulator: pfuze100: Don't allocate an invalid gpio
drivers/regulator/pfuze100-regulator.c | 5 +++++
1 file changed, 5 insertions(+)
--
2.0.0.rc2
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2014-05-26 8:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 8:45 Sean Cross [this message]
[not found] ` <1401093941-12386-1-git-send-email-xobs-nXMMniAx+RbQT0dZR+AlfA@public.gmane.org>
2014-05-26 8:45 ` [PATCH 1/2] regulator: pfuze100: Support SWB enable/disable Sean Cross
[not found] ` <1401093941-12386-2-git-send-email-xobs-nXMMniAx+RbQT0dZR+AlfA@public.gmane.org>
2014-05-26 14:57 ` Mark Brown
[not found] ` <20140526145739.GO22111-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-05-26 15:27 ` Sean Cross
2014-05-26 8:45 ` [PATCH 2/2] regulator: pfuze100: Don't allocate an invalid gpio Sean Cross
2014-05-26 15:45 ` [PATCH 0/2] regulator: pfuze100: Minor driver enhancements Mark Brown
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=1401093941-12386-1-git-send-email-xobs@kosagi.com \
--to=xobs-nxmmniax+rbqt0dzr+alfa@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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).