From: Andy Duan <fugang.duan@nxp.com>
To: Fabio Estevam <festevam@gmail.com>,
Sven Van Asbroeck <thesven73@gmail.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: RE: [EXT] Re: [PATCH v4 2/2] ARM: imx6plus: enable internal routing of clk_enet_ref where possible
Date: Tue, 30 Jun 2020 02:24:42 +0000 [thread overview]
Message-ID: <AM6PR0402MB360700E4C52AE36CC3176622FF6F0@AM6PR0402MB3607.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <CAOMZO5Cr3k+oy_Sf0kL9gge7bwqkvJR8BQhY-FvxVXN00A2ARw@mail.gmail.com>
From: Fabio Estevam <festevam@gmail.com> Sent: Monday, June 29, 2020 10:26 PM
> Hi Sven,
>
> On Mon, Jun 29, 2020 at 10:40 AM Sven Van Asbroeck
> <thesven73@gmail.com> wrote:
>
> > Thank you for testing this out on a different platform !
> >
> > I had a look at how things are done in the Freescale fork of the
> > kernel
> > (5.4.24_2.1.0) and I noticed that this kernel has almost the same
> > behaviour as this proposed patch: the GPR5 bit is _always_ set on a
> > plus. The code does not check how the enet clock is generated.
> >
> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsour
> >
> ce.codeaurora.org%2Fexternal%2Fimx%2Flinux-imx%2Ftree%2Farch%2Farm
> %2Fm
> >
> ach-imx%2Fmach-imx6q.c%3Fh%3Drel_imx_5.4.24_2.1.0%26id%3Dbabac00
> 8e5cf1
> >
> 68abca1a85bda2e8071ca27a5c0%23n269&data=02%7C01%7Cfugang.d
> uan%40nx
> >
> p.com%7C8570de0304514796ea0208d81c385a11%7C686ea1d3bc2b4c6fa92
> cd99c5c3
> >
> 01635%7C0%7C1%7C637290375659016888&sdata=I9werBT%2FDkcWu
> LEKlFVzRi2
> > KD%2FLwPz2QCqw%2BHn0HY8U%3D&reserved=0
> >
> > Now, I'm assuming that the sabresd-plus can run on the Freescale
> > kernel fork. The GPR5 bit will always be set there.
>
> Just tested 5.4.24_2.1.0 on an imx6qp sabresd and DHCP also fails there.
Fabio, we have LAVA daily test by networking for imx6qp sabresd board, no any issue found.
Please double check the issue on your local.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-06-30 2:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 14:01 [PATCH v4 1/2] ARM: imx: mach-imx6q: Search for fsl, imx6q-iomuxc-gpr earlier Sven Van Asbroeck
2020-06-25 14:01 ` [PATCH v4 2/2] ARM: imx6plus: enable internal routing of clk_enet_ref where possible Sven Van Asbroeck
2020-06-28 5:05 ` [EXT] " Andy Duan
2020-06-29 13:09 ` Fabio Estevam
2020-06-29 13:40 ` Sven Van Asbroeck
2020-06-29 14:04 ` Fabio Estevam
2020-06-29 14:25 ` Fabio Estevam
2020-06-29 14:37 ` Sven Van Asbroeck
2020-06-30 6:36 ` [EXT] " Andy Duan
2020-06-30 11:49 ` Fabio Estevam
2020-07-01 1:31 ` Andy Duan
2020-06-30 15:23 ` Sven Van Asbroeck
2020-07-01 3:18 ` Andy Duan
2020-07-01 3:39 ` Fabio Estevam
2020-07-01 3:42 ` Andy Duan
2020-07-01 3:45 ` Fabio Estevam
2020-07-01 13:51 ` Sven Van Asbroeck
2020-07-01 15:30 ` Andy Duan
2020-07-01 16:03 ` Sven Van Asbroeck
2020-07-01 16:39 ` Fabio Estevam
2020-06-30 2:24 ` Andy Duan [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=AM6PR0402MB360700E4C52AE36CC3176622FF6F0@AM6PR0402MB3607.eurprd04.prod.outlook.com \
--to=fugang.duan@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=thesven73@gmail.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).