Netdev List
 help / color / mirror / Atom feed
From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
To: Philippe Schenker <philippe.schenker@toradex.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"embed3d@gmail.com" <embed3d@gmail.com>,
	"qiangqing.zhang@nxp.com" <qiangqing.zhang@nxp.com>
Cc: "philipp.rossak@formulastudent.de"
	<philipp.rossak@formulastudent.de>,
	"guoniu.zhou@nxp.com" <guoniu.zhou@nxp.com>,
	"aisheng.dong@nxp.com" <aisheng.dong@nxp.com>,
	"abel.vesa@nxp.com" <abel.vesa@nxp.com>,
	"andrew@lunn.ch" <andrew@lunn.ch>,
	"linux-imx@nxp.com" <linux-imx@nxp.com>
Subject: Re: Question: Ethernet Phy issues on Colibri IMX8X (imx8qxp) - kernel 5.19
Date: Wed, 31 Aug 2022 08:12:41 +0000	[thread overview]
Message-ID: <fe0d235ff45dea2cd808b0d86b5601b333915fd4.camel@toradex.com> (raw)
In-Reply-To: <e17a49d75fa8fe36af30ff1c2b1c981375c94541.camel@toradex.com>

On Thu, 2022-08-11 at 08:07 +0000, Philippe Schenker wrote:
> On Wed, 2022-08-10 at 20:40 +0200, Philipp Rossak wrote:
> > > Hi Marcel,
> > > 
> > > thanks!
> > > 
> > > With the removed line it is working now!
> > > 
> > > I hope there will be a mainlined solution soon.

Yes, I am still hoping for more information from NXP on that matter.

@NXP: Anybody?

> This is an interesting question. Since it's a SCFW issue and a general
> question about these SoCs, I'll take the liberty of hijacking this
> thread for some questions (since NXP is also in the loop now).
> 
> @NXP people: which SCFW version should be used in general with mainline
> linux-kernel ?
> And how is it planned to proceed with SC-firmware enabled SoCs on
> mainline linux?
> Is the SCFW API backward compatible?
> If so, from which version on?
> 
> Thanks in advance for enlightening us all on this SCFW issue.
> 
> Philippe
> 
> > > Cheers
> > > Philipp
> > > 
> > > On 10.08.22 10:05, Marcel Ziswiler wrote:
> > > > > Sali Philipp
> > > > > 
> > > > > On Wed, 2022-08-10 at 00:55 +0200, Philipp Rossak wrote:
> > > > > > > Hi,
> > > > > > > 
> > > > > > > I currently have a project with a Toradex Colibri IMX8X SOM
> > > > > > > board> >> whith
> > > > > > > an onboard Micrel KSZ8041NL Ethernet PHY.
> > > > > > > 
> > > > > > > The hardware is described in the devictree properly so I
> > > > > > > expected> >> that
> > > > > > > the onboard Ethernet with the phy is working.
> > > > > > > 
> > > > > > > Currently I'm not able to get the link up.
> > > > > > > 
> > > > > > > I already compared it to the BSP kernel, but I didn't found>
> > > > > > > > > anything
> > > > > > > helpful. The BSP kernel is working.
> > > > > > > 
> > > > > > > Do you know if there is something in the kernel missing and
> > > > > > > got it> >> running?
> > > > > 
> > > > > Yes, you may just revert the following commit babfaa9556d7
> > > > > ("clk:> >imx: scu: add more scu clocks")
> > > > > 
> > > > > Alternatively, just commenting out the following single line
> > > > > also> >helps:
> > > > > 
> > > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/clk/imx/clk-imx8qxp.c?h=v5.19#n172
> > > > > 
> > > > > I just found this out about two weeks ago before I went to
> > > > > vacation> >and since have to find out with NXP what
> > > > > exactly the idea of this clocking/SCFW stuff is related to our>
> > > > > > hardware.
> > > > > 
> > > > > @NXP: If any of you guys could shed some light that would be
> > > > > much> >appreciated. Thanks!
> > > > > 
> > > > > > > Thanks,
> > > > > > > Philipp
> > > > > 
> > > > > Cheers
> > > > > 
> > > > > Marcel

      reply	other threads:[~2022-08-31  8:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09 22:55 Question: Ethernet Phy issues on Colibri IMX8X (imx8qxp) - kernel 5.19 Philipp Rossak
2022-08-10  1:19 ` Andrew Lunn
2022-08-10  7:20   ` Philipp Rossak
2022-08-10  8:05 ` Marcel Ziswiler
2022-08-10  8:49   ` Aisheng Dong
2022-08-10 18:40   ` Philipp Rossak
2022-08-11  8:07     ` Philippe Schenker
2022-08-31  8:12       ` Marcel Ziswiler [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=fe0d235ff45dea2cd808b0d86b5601b333915fd4.camel@toradex.com \
    --to=marcel.ziswiler@toradex.com \
    --cc=abel.vesa@nxp.com \
    --cc=aisheng.dong@nxp.com \
    --cc=andrew@lunn.ch \
    --cc=embed3d@gmail.com \
    --cc=guoniu.zhou@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=netdev@vger.kernel.org \
    --cc=philipp.rossak@formulastudent.de \
    --cc=philippe.schenker@toradex.com \
    --cc=qiangqing.zhang@nxp.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