From: Michael Tremer <michael.tremer@ipfire.org>
To: sig-arm@lists.ipfire.org
Subject: Re: ClearFog PCIe not working with v2.21-core126
Date: Fri, 15 Feb 2019 11:34:03 +0000 [thread overview]
Message-ID: <1E2E2227-9F33-4C8A-A036-3890668673DE@ipfire.org> (raw)
In-Reply-To: <CAEzXK1r3qLzCQKvg3Oe4mrpjbFAJH7wzvUmow+usMqvfsDgEcA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]
Hello Luis,
Thank you for writing.
I think there should be no problem to enable these options.
Would you please open a ticket on our Bugzilla and I will assign it to the right person?
Best,
-Michael
> On 14 Feb 2019, at 19:53, Luís Mendes <luis.p.mendes(a)gmail.com> wrote:
>
> Hi all,
>
> I noticed that the ipfire kernel configuration doesn't include the
> driver for I2C GPIO expander chip PCA9655 which is a required
> dependency for the PCIe controller. Since the PCIe card reset and
> clock request signals are provided by this expander chip, without such
> driver, Linux simply ignores the entire PCIe subsystem.
>
> I've tested that adding the following options to the kernel
> configuration fixes the issue:
> CONFIG_GPIO_PCA953X=y
> CONFIG_GPIO_PCA953X_IRQ=y
>
> Unfortunately IRQ option is only available is module is complied as
> kernel built-in. IRQ is relevant, because the USB subsystem relies on
> it to monitor USB port OverCurrent conditions, through the same GPIO
> expander chip.
>
> Can these kernel configurations option be added to ipfire? It would be
> relevant to allow for additional Ethernet ports.
>
> Regards,
> Luís Mendes
> _______________________________________________
> SIG-ARM mailing list
> SIG-ARM(a)lists.ipfire.org
> https://lists.ipfire.org/mailman/listinfo/sig-arm
prev parent reply other threads:[~2019-02-15 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEzXK1rRggrGTz9yJMP_aukugCgBJaL3mYwnd8s5+ocVxZQsmw@mail.gmail.com>
2019-02-14 19:53 ` Luís Mendes
2019-02-15 11:34 ` Michael Tremer [this message]
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=1E2E2227-9F33-4C8A-A036-3890668673DE@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=sig-arm@lists.ipfire.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