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 12:19:02 +0000 [thread overview]
Message-ID: <52A706B6.1030400@einfach.org> (raw)
In-Reply-To: <20131210114427.GU16823@kw.sim.vm.gnt>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/10/2013 11:44 AM, Simon Guinot wrote:
>> 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
>
> You can enforce the driver loading with the kernel parameter
> acpi_enforce_resources={lax|no}.
Thank you! Yes, this way I can load it and get sensor data. There are
no resource conflicts:
# cat /proc/ioports |grep "sch\|dme"
0647-0647 : sch311x_wdt
064b-0650 : gpio-sch311x
0665-0668 : sch311x_wdt
0670-0671 : dme1737
0670-0671 : dme1737
> Yes indeed. I guess this kind of devices with common resources
> could really make use of a mfd driver.
Maybe, but I'm not going to do the work...
bruno
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
iQEcBAEBAgAGBQJSpwa2AAoJEE06nu8QSdWBpfoH/3ste3Bn4YixePdu9CMKqaFq
jQEu6MsDm7j96Iq9sk9DMyropcqeyZd0vtM9AlTVYPQCLR4fFU7oEa+HDrFa1OUz
TjphDkgSFl4hHXxirHH4GP9YadBDwCfw/6EF8B/LasdHmM4OeBA8ucFRx/LFbWcH
IfPCCgCz55DizXLvDcEvEUkdgD5nEwXSR4GKjX5djR7+dRNAvSl1Yg8rB9BXw/1p
T/CO6V5N/2US0cV1t/Hqql2+r0ZlrYRwm4e/pnieGxtdivWsQN+BBBpVgRKRhri0
oHi5MV7ZBw9vx2Y70rV48S6CdUzk0j3j6+WQDl4khtjLDjg1VH4e6QsfXf1dK8Q=
=fYLG
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-12-10 12:19 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
2013-12-10 11:44 ` Simon Guinot
2013-12-10 12:19 ` Bruno Randolf [this message]
-- 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=52A706B6.1030400@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 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).