linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>
Cc: "Hauke Mehrtens" <hauke@hauke-m.de>, "Rafał Miłecki" <zajec5@gmail.com>
Subject: [3.14 FIX][PATCH] bcma: gpio: register all 32 GPIOs
Date: Thu, 13 Feb 2014 18:06:26 +0100	[thread overview]
Message-ID: <1392311186-7805-1-git-send-email-zajec5@gmail.com> (raw)

Broadcom boards have 32 GPIOs (not 16) and these higher ones are
actually used on some devices (for buttons, reset of WiFi devices).

Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
---
Similar patch may be needed for ssb, however I didn't meet any ssb SoC
with GPIOs 16-31 connected to anything.
This is so trivial I hope it can go as a fix for 3.14. It allows support
for some devices that use these higher GPIOs.
---
 drivers/bcma/driver_gpio.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/bcma/driver_gpio.c b/drivers/bcma/driver_gpio.c
index 25f9887..2f0ceac 100644
--- a/drivers/bcma/driver_gpio.c
+++ b/drivers/bcma/driver_gpio.c
@@ -218,7 +218,7 @@ int bcma_gpio_init(struct bcma_drv_cc *cc)
 #if IS_BUILTIN(CONFIG_BCMA_HOST_SOC)
 	chip->to_irq		= bcma_gpio_to_irq;
 #endif
-	chip->ngpio		= 16;
+	chip->ngpio		= 32;
 	/* There is just one SoC in one device and its GPIO addresses should be
 	 * deterministic to address them more easily. The other buses could get
 	 * a random base number. */
-- 
1.8.4.5


             reply	other threads:[~2014-02-13 17:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 17:06 Rafał Miłecki [this message]
2014-02-13 20:04 ` [3.14 FIX][PATCH] bcma: gpio: register all 32 GPIOs Rafał Miłecki
2014-02-13 23:23   ` John W. Linville
2014-02-13 23:34 ` Hauke Mehrtens
2014-02-14 12:01   ` Rafał Miłecki
2014-02-14 14:27     ` John W. Linville
2014-02-14 15:40       ` Rafał Miłecki

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=1392311186-7805-1-git-send-email-zajec5@gmail.com \
    --to=zajec5@gmail.com \
    --cc=hauke@hauke-m.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).