From: Peter Tyser <ptyser@xes-inc.com>
To: linux-kernel@vger.kernel.org
Cc: Peter Tyser <ptyser@xes-inc.com>,
tomoya-linux@dsn.okisemi.com,
Grant Likely <grant.likely@secretlab.ca>
Subject: [PATCH] gpio: ml_ioh_gpio: Fix output value of ioh_gpio_direction_output()
Date: Thu, 24 Mar 2011 18:17:14 -0500 [thread overview]
Message-ID: <1301008634-25429-1-git-send-email-ptyser@xes-inc.com> (raw)
The ioh_gpio_direction_output() function was missing a write to set the
desired output value. The function would properly set the GPIO
direction, but not the output value. The value would have to manually
be set with a follow up call to ioh_gpio_set().
Add the missing write so that ioh_gpio_direction_output() sets both the
GPIO direction and value.
Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
Cc: tomoya-linux@dsn.okisemi.com
Cc: Grant Likely <grant.likely@secretlab.ca>
---
This is untested - just noticed it while working on an unrelated change. An
ack or tested-by from someone with real hardware would be appreciated.
drivers/gpio/ml_ioh_gpio.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/gpio/ml_ioh_gpio.c b/drivers/gpio/ml_ioh_gpio.c
index cead8e6..7a0423c 100644
--- a/drivers/gpio/ml_ioh_gpio.c
+++ b/drivers/gpio/ml_ioh_gpio.c
@@ -116,6 +116,7 @@ static int ioh_gpio_direction_output(struct gpio_chip *gpio, unsigned nr,
reg_val |= (1 << nr);
else
reg_val &= ~(1 << nr);
+ iowrite32(reg_val, &chip->reg->regs[chip->ch].po);
mutex_unlock(&chip->lock);
--
1.7.0.4
next reply other threads:[~2011-03-24 23:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 23:17 Peter Tyser [this message]
2011-03-25 0:31 ` Tomoya MORINAGA
2011-03-25 14:47 ` Peter Tyser
2011-03-28 0:56 ` Tomoya MORINAGA
2011-03-25 15:04 ` [PATCH] gpio: pch_gpio: Fix output value of pch_gpio_direction_output() Peter Tyser
2011-03-31 21:16 ` Grant Likely
2011-03-31 21:17 ` Grant Likely
2011-03-31 21:18 ` [PATCH] gpio: ml_ioh_gpio: Fix output value of ioh_gpio_direction_output() Grant Likely
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=1301008634-25429-1-git-send-email-ptyser@xes-inc.com \
--to=ptyser@xes-inc.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=tomoya-linux@dsn.okisemi.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
all inboxes | Powered by JetHome®