From: Nick Bowler <nbowler@draconx.ca>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Rob Herring <robh@kernel.org>,
Saravana Kannan <saravanak@google.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: PROBLEM: Broken or delayed ethernet on Xilinx ZCU104 since 5.18 (regression)
Date: Sat, 5 Aug 2023 03:34:22 -0400 [thread overview]
Message-ID: <CADyTPEyQcHd5-A2TLf_-U5KdtA5WKZ_mNYKvx3DSMjkNi99E0g@mail.gmail.com> (raw)
In-Reply-To: <c38e208b-4ffa-4310-ae00-412447fc4269@lunn.ch>
On 2023-08-05, Andrew Lunn <andrew@lunn.ch> wrote:
>> > It was also commented out before that change. It could be that gpio
>> > controller is missing. Do you have the driver for the tca6416 in
>> > your kernel configuration?
>>
>> I have CONFIG_GPIO_PCA953X=y which I think is the correct driver?
>
> It does appear to be the correct driver. But check if it has
> loaded. It is an i2c device, so maybe you are missing the I2C bus
> master device?
That's it! I needed to set
CONFIG_I2C_CADENCE=y
and now things are working again!
Thanks,
Nick
next prev parent reply other threads:[~2023-08-05 7:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 15:26 PROBLEM: Broken or delayed ethernet on Xilinx ZCU104 since 5.18 (regression) Nick Bowler
2023-08-04 15:45 ` Linux regression tracking (Thorsten Leemhuis)
2023-08-08 16:00 ` Robert Hancock
2023-08-04 15:52 ` Rob Herring
2023-08-04 16:24 ` Nick Bowler
2023-08-04 16:28 ` Nick Bowler
2023-08-04 16:47 ` Russell King (Oracle)
2023-08-04 16:54 ` Nick Bowler
2023-08-04 17:02 ` Rob Herring
2023-08-04 17:52 ` Nick Bowler
2023-08-04 20:22 ` Rob Herring
2023-08-04 21:31 ` Nick Bowler
2023-08-04 22:27 ` Russell King (Oracle)
2023-08-05 6:57 ` Nick Bowler
2023-08-05 7:03 ` Andrew Lunn
2023-08-05 6:58 ` Andrew Lunn
2023-08-05 7:10 ` Nick Bowler
2023-08-05 7:25 ` Andrew Lunn
2023-08-05 7:34 ` Nick Bowler [this message]
2023-08-29 13:30 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-08-05 1:03 ` Saravana Kannan
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=CADyTPEyQcHd5-A2TLf_-U5KdtA5WKZ_mNYKvx3DSMjkNi99E0g@mail.gmail.com \
--to=nbowler@draconx.ca \
--cc=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=robh@kernel.org \
--cc=saravanak@google.com \
/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).