From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?utf-8?q?Lu=C3=ADs?= Mendes <luis.p.mendes@gmail.com>
To: sig-arm@lists.ipfire.org
Subject: Re: SIG-ARM Digest, Vol 21, Issue 1
Date: Fri, 15 Feb 2019 16:27:10 +0000
Message-ID:
 <CAEzXK1pDM0bHswsejBCyjwkFHrrRG1wb_gxnpwBDR5APzmFWfQ@mail.gmail.com>
In-Reply-To: <mailman.3.1550232002.25851.sig-arm@lists.ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7802680112293269380=="
List-Id: <sig-arm.lists.ipfire.org>

--===============7802680112293269380==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi Michael,

I've just created bug report 12000 in Bugzilla, as per your request.
Bug 12000 - ClearFog PCIe not working with v2.21-core126

Regards,
Lu=C3=ADs Mendes

On Fri, Feb 15, 2019 at 12:00 PM <sig-arm-request(a)lists.ipfire.org> wrote:
>
> Send SIG-ARM mailing list submissions to
>         sig-arm(a)lists.ipfire.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.ipfire.org/mailman/listinfo/sig-arm
> or, via email, send a message with subject or body 'help' to
>         sig-arm-request(a)lists.ipfire.org
>
> You can reach the person managing the list at
>         sig-arm-owner(a)lists.ipfire.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of SIG-ARM digest..."
>
>
> Today's Topics:
>
>    1. ClearFog PCIe not working with v2.21-core126 (Lu?s Mendes)
>    2. Re: ClearFog PCIe not working with v2.21-core126 (Michael Tremer)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 14 Feb 2019 19:53:46 +0000
> From: Lu?s Mendes <luis.p.mendes(a)gmail.com>
> To: sig-arm(a)lists.ipfire.org
> Subject: ClearFog PCIe not working with v2.21-core126
> Message-ID:
>         <CAEzXK1r3qLzCQKvg3Oe4mrpjbFAJH7wzvUmow+usMqvfsDgEcA(a)mail.gmail.c=
om>
> Content-Type: text/plain; charset=3D"UTF-8"
>
> 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=3Dy
> CONFIG_GPIO_PCA953X_IRQ=3Dy
>
> 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
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 15 Feb 2019 11:34:03 +0000
> From: Michael Tremer <michael.tremer(a)ipfire.org>
> To: Lu?s Mendes <luis.p.mendes(a)gmail.com>
> Cc: sig-arm(a)lists.ipfire.org
> Subject: Re: ClearFog PCIe not working with v2.21-core126
> Message-ID: <1E2E2227-9F33-4C8A-A036-3890668673DE(a)ipfire.org>
> Content-Type: text/plain;       charset=3Dutf-8
>
> 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=3Dy
> > CONFIG_GPIO_PCA953X_IRQ=3Dy
> >
> > 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
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> SIG-ARM mailing list
> SIG-ARM(a)lists.ipfire.org
> https://lists.ipfire.org/mailman/listinfo/sig-arm
>
>
> ------------------------------
>
> End of SIG-ARM Digest, Vol 21, Issue 1
> **************************************

--===============7802680112293269380==--