From: Fabio Estevam <festevam@gmail.com>
To: Bruno Thomsen <bruno.thomsen@gmail.com>
Cc: Shawn Guo <shawnguo@kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
Bruno Thomsen <bth@kamstrup.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Subject: Re: [PATCH 2/3] ARM: dts: imx7: add support for kamstrup flex concentrator
Date: Tue, 14 Jul 2020 08:54:06 -0300 [thread overview]
Message-ID: <CAOMZO5DsyqRgD8n-w=6OmnXuMX+1T2DDOjQLNK133=FaqtWXVQ@mail.gmail.com> (raw)
In-Reply-To: <CAH+2xPAHKY6YfhO-jXfKN+TRN5LDT1Kkn8a8HUj_EOqFt=75nQ@mail.gmail.com>
Hi Bruno,
On Tue, Jul 14, 2020 at 7:03 AM Bruno Thomsen <bruno.thomsen@gmail.com> wrote:
> I have not yet been successful in converting the deprecated properties
> to generic phy properties, so hoping I could get a hit.
>
> Kernel error messages:
> mdio_bus 30be0000.ethernet-1: MDIO device at address 1 is missing.
Please double-check whether 1 is the correct address for the KSZ8051
Ethernet PHY as per your schematics.
Are there external pull-up/pull-down resistors for strapping the
various configuration pins for the PHY? Or are the pull-up/pull-down
provided by the i.MX7D pins?
If there are no external pull-ups, please make sure to configure the
pinctrl_enet1 accordingly, so that the Ethernet PHY address can be
properly configured and then mdio_bus driver can find it at the
correct address.
Please check in arch/arm/boot/dts/imx6qdl-sr-som.dtsi for an example
on how to configure the Ethernet PHY pin strapping via iMX IOMUX.
WARNING: multiple messages have this Message-ID (diff)
From: Fabio Estevam <festevam@gmail.com>
To: Bruno Thomsen <bruno.thomsen@gmail.com>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Bruno Thomsen <bth@kamstrup.com>,
Rob Herring <robh+dt@kernel.org>,
NXP Linux Team <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: [PATCH 2/3] ARM: dts: imx7: add support for kamstrup flex concentrator
Date: Tue, 14 Jul 2020 08:54:06 -0300 [thread overview]
Message-ID: <CAOMZO5DsyqRgD8n-w=6OmnXuMX+1T2DDOjQLNK133=FaqtWXVQ@mail.gmail.com> (raw)
In-Reply-To: <CAH+2xPAHKY6YfhO-jXfKN+TRN5LDT1Kkn8a8HUj_EOqFt=75nQ@mail.gmail.com>
Hi Bruno,
On Tue, Jul 14, 2020 at 7:03 AM Bruno Thomsen <bruno.thomsen@gmail.com> wrote:
> I have not yet been successful in converting the deprecated properties
> to generic phy properties, so hoping I could get a hit.
>
> Kernel error messages:
> mdio_bus 30be0000.ethernet-1: MDIO device at address 1 is missing.
Please double-check whether 1 is the correct address for the KSZ8051
Ethernet PHY as per your schematics.
Are there external pull-up/pull-down resistors for strapping the
various configuration pins for the PHY? Or are the pull-up/pull-down
provided by the i.MX7D pins?
If there are no external pull-ups, please make sure to configure the
pinctrl_enet1 accordingly, so that the Ethernet PHY address can be
properly configured and then mdio_bus driver can find it at the
correct address.
Please check in arch/arm/boot/dts/imx6qdl-sr-som.dtsi for an example
on how to configure the Ethernet PHY pin strapping via iMX IOMUX.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-07-14 11:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 11:49 [PATCH 1/3] dt-bindings: ARM: imx: add kamstrup flex concentrator to schema Bruno Thomsen
2020-06-29 11:49 ` Bruno Thomsen
2020-06-29 11:49 ` [PATCH 2/3] ARM: dts: imx7: add support for kamstrup flex concentrator Bruno Thomsen
2020-06-29 11:49 ` Bruno Thomsen
2020-07-13 2:52 ` Shawn Guo
2020-07-13 2:52 ` Shawn Guo
2020-07-14 10:03 ` Bruno Thomsen
2020-07-14 10:03 ` Bruno Thomsen
2020-07-14 11:54 ` Fabio Estevam [this message]
2020-07-14 11:54 ` Fabio Estevam
2020-07-15 14:21 ` Bruno Thomsen
2020-07-15 14:21 ` Bruno Thomsen
2020-07-15 20:28 ` Fabio Estevam
2020-07-15 20:28 ` Fabio Estevam
2020-06-29 11:49 ` [PATCH 3/3] MAINTAINERS: Add Bruno Thomsen as reviewer of Kamstrup DTS Bruno Thomsen
2020-06-29 11:49 ` Bruno Thomsen
2020-07-13 2:56 ` Shawn Guo
2020-07-13 2:56 ` Shawn Guo
2020-07-13 5:22 ` Joe Perches
2020-07-13 5:22 ` Joe Perches
2020-07-13 7:13 ` Shawn Guo
2020-07-13 7:13 ` Shawn Guo
2020-07-13 7:26 ` Joe Perches
2020-07-13 7:26 ` Joe Perches
2020-07-13 7:31 ` Bruno Thomsen
2020-07-13 7:31 ` Bruno Thomsen
2020-07-13 2:32 ` [PATCH 1/3] dt-bindings: ARM: imx: add kamstrup flex concentrator to schema Shawn Guo
2020-07-13 2:32 ` Shawn Guo
2020-07-15 20:26 ` Rob Herring
2020-07-15 20:26 ` Rob Herring
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='CAOMZO5DsyqRgD8n-w=6OmnXuMX+1T2DDOjQLNK133=FaqtWXVQ@mail.gmail.com' \
--to=festevam@gmail.com \
--cc=bruno.thomsen@gmail.com \
--cc=bth@kamstrup.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.