public inbox for sig-arm@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Luís Mendes" <luis.p.mendes@gmail.com>
To: sig-arm@lists.ipfire.org
Subject: ClearFog PCIe not working with v2.21-core126
Date: Thu, 14 Feb 2019 19:53:46 +0000	[thread overview]
Message-ID: <CAEzXK1r3qLzCQKvg3Oe4mrpjbFAJH7wzvUmow+usMqvfsDgEcA@mail.gmail.com> (raw)
In-Reply-To: <CAEzXK1rRggrGTz9yJMP_aukugCgBJaL3mYwnd8s5+ocVxZQsmw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 838 bytes --]

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

       reply	other threads:[~2019-02-14 19:53 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 [this message]
2019-02-15 11:34   ` Michael Tremer

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=CAEzXK1r3qLzCQKvg3Oe4mrpjbFAJH7wzvUmow+usMqvfsDgEcA@mail.gmail.com \
    --to=luis.p.mendes@gmail.com \
    --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