From: Bruno Randolf <br1@einfach.org>
To: Simon Guinot <simon.guinot@sequanux.org>
Cc: linus.walleij@linaro.org, wim@iguana.be, linux-gpio@vger.kernel.org
Subject: Re: [PATCH] gpio: add GPIO support for SMSC SCH311x
Date: Tue, 10 Dec 2013 10:18:12 +0000 [thread overview]
Message-ID: <52A6EA64.4040307@einfach.org> (raw)
In-Reply-To: <20131205165647.GM16823@kw.sim.vm.gnt>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/05/2013 04:56 PM, Simon Guinot wrote:
> Note that this base address is shared between several drivers:
> watchdog/sch311x_wdt, hwmon/dme1737 and gpio/gpio-sch311x.c. The
> same logical device (0xa) is used.
>
> Moreover some offsets against this base address are also shared.
> For example, 0x47 is a "valid" offset for both the GPIO and the
> watchdog drivers. I guess that the correct usage for this pin
> depends on how the hardware is wired. Unfortunately, there is no
> way for the drivers to guess that.
>
> Did you had the opportunity to run all this drivers together ?
My access to the board is limited, but I had a chance to try it.
dme1737 doesn't load because there is another resource conflict:
# modprobe dme1737
FATAL: Error inserting dme1737
(/lib/modules/3.13.0-rc1-wl+/kernel/drivers/hwmon/dme1737.ko): Device
or resource busy
[ 181.109897] ACPI Warning: 0x00000670-0x00000671 SystemIO conflicts
with Region \_SB_.PCI0.LPCB.RNTR 1 (20130927/utaddress-251)
[ 181.109921] ACPI: If an ACPI driver is available for this device,
you should use it instead of the native driver
I can load and use sch311x_wdt and gpio-sch311x at the same time,
because they reserve different memory regions:
/proc/ioports:
0647-0647 : sch311x_wdt
064b-0650 : gpio-sch311x
0665-0668 : sch311x_wdt
Only when I'd try to request GPIO 60 (offset 0x47) I obviously get a
conflict:
# echo 60 > /sys/class/gpio/export
- -bash: echo: write error: Device or resource busy
[ 334.776859] gpio-sch311x gpio-sch311x: Failed to request region 0x0647.
I think this can be expected...
bruno
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
iQEcBAEBAgAGBQJSpupkAAoJEE06nu8QSdWBvXYH/jE9AG5YtidekEPJS7REYLNJ
hrAgykvnthDSACSPp6jLZnA4Bh80EG5DZGJ0PwtmXmR701+cOfcqlwwFvsfvHgXk
YHxihi+niwZ8p04njwAk3sWPtODprbcboB+G4USjoVeZwDInKx8gLgiKHho7akbR
PRht6cWm6iwX7UeE1/1/BfSUHisi8L0OBCditDLBApEcw094UXxP1juqQimXz2xV
Tver8mRkOYUl7q0VT7j6WIqIaw2yq+a4QEbjoSarc3YwbYuEMYzOyevI61uczhej
Sq7sXYvkTcos2k8dQMr33oM89uJ+hgBOja9Ir2tInR1ewDjLnbzCtV+n5Q8SJLg=
=E2V6
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-12-10 10:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 0:18 [PATCH] gpio: add GPIO support for SMSC SCH311x Bruno Randolf
2013-11-29 14:40 ` Linus Walleij
2013-11-29 15:02 ` Mika Westerberg
2013-11-29 19:55 ` Linus Walleij
2013-11-29 17:21 ` Bruno Randolf
2013-11-29 20:00 ` Linus Walleij
2013-11-29 20:37 ` Simon Guinot
2013-12-04 12:33 ` Linus Walleij
2013-11-29 18:56 ` Simon Guinot
2013-12-02 12:43 ` Bruno Randolf
2013-12-05 16:56 ` Simon Guinot
2013-12-10 10:18 ` Bruno Randolf [this message]
2013-12-10 11:44 ` Simon Guinot
2013-12-10 12:19 ` Bruno Randolf
-- strict thread matches above, loose matches on Subject: below --
2013-12-04 0:23 Bruno Randolf
2013-12-04 1:06 ` David Cohen
2013-12-10 11:51 ` Linus Walleij
2013-12-10 17:05 ` Matthew Garrett
2013-12-11 4:05 ` Vivien Didelot
2013-12-12 19:50 ` Linus Walleij
2013-12-16 2:46 ` Vivien Didelot
2013-12-20 9:07 ` Linus Walleij
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=52A6EA64.4040307@einfach.org \
--to=br1@einfach.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=simon.guinot@sequanux.org \
--cc=wim@iguana.be \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.