From: "Arınç ÜNAL" <arinc.unal@arinc9.com>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Sander Vanheule <sander@svanheule.net>,
NeilBrown <neil@brown.name>, DENG Qingfang <dqfext@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
erkin.bozoglu@xeront.com, linux-staging@lists.linux.dev
Subject: Re: [PATCH 2/2] staging: mt7621-dts: do not use rgmii2_pins for ethernet on GB-PC1
Date: Tue, 15 Feb 2022 11:49:45 +0300 [thread overview]
Message-ID: <d9240058-68b4-cbd6-54b0-18f41ee5a98a@arinc9.com> (raw)
In-Reply-To: <CAMhs-H-74bK3m975Dtmg2zPrGjmqzSd+Tb_qdUV14yJBAWRQbw@mail.gmail.com>
Hey Sergio,
On 15/02/2022 11:35, Sergio Paracuellos wrote:
> Hi Arinc,
>
> On Tue, Feb 15, 2022 at 9:18 AM Arınç ÜNAL <arinc.unal@arinc9.com> wrote:
>>
>> GB-PC1 uses some of the rgmii2 pins (22 - 33) as GPIO. Therefore, the
>> rgmii2 bus cannot be used on this device.
>> Overwrite pinctrl-0 property under the ethernet node without rgmii2_pins on
>> the GB-PC1 devicetree.
>>
>> Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
>> ---
>> drivers/staging/mt7621-dts/gbpc1.dts | 4 ++++
>> 1 file changed, 4 insertions(+)
>
> No issues in GB-PC1. So:
>
> Tested-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Thanks for testing it so quickly!
I was wondering if you got pinctrl errors on the bootlog before applying
this patch series.
rgmii2 pin group is given gpio function so calling it from ethernet node
would cause this on my TP-Link RE650 v1 which also uses the rgmii2_pins
as GPIO.
[ 1.177349] rt2880-pinmux pinctrl: pin io22 already requested by
pinctrl; cannot claim for 1e100000.ethernet
[ 1.196966] rt2880-pinmux pinctrl: pin-22 (1e100000.ethernet) status -22
[ 1.210312] rt2880-pinmux pinctrl: could not request pin 22 (io22)
from group rgmii2 on device rt2880-pinmux
[ 1.230058] mtk_soc_eth 1e100000.ethernet: Error applying setting,
reverse things back
[ 1.245853] mtk_soc_eth: probe of 1e100000.ethernet failed with error -22
Arınç
next prev parent reply other threads:[~2022-02-15 8:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 8:17 [PATCH 1/2] staging: mt7621-dts: fix pinctrl-0 items to be size-1 items on ethernet Arınç ÜNAL
2022-02-15 8:17 ` [PATCH 2/2] staging: mt7621-dts: do not use rgmii2_pins for ethernet on GB-PC1 Arınç ÜNAL
2022-02-15 8:35 ` Sergio Paracuellos
2022-02-15 8:49 ` Arınç ÜNAL [this message]
2022-02-15 9:09 ` Sergio Paracuellos
2022-02-15 14:11 ` Arınç ÜNAL
2022-02-15 15:16 ` Sergio Paracuellos
2022-02-27 15:11 ` Arınç ÜNAL
2022-02-28 7:01 ` Sergio Paracuellos
2022-02-28 14:53 ` Arınç ÜNAL
2022-02-28 15:11 ` Sergio Paracuellos
2022-03-03 15:16 ` Arınç ÜNAL
2022-03-07 22:25 ` Arınç ÜNAL
2022-03-08 12:52 ` Sergio Paracuellos
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=d9240058-68b4-cbd6-54b0-18f41ee5a98a@arinc9.com \
--to=arinc.unal@arinc9.com \
--cc=andrew@lunn.ch \
--cc=dqfext@gmail.com \
--cc=erkin.bozoglu@xeront.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-staging@lists.linux.dev \
--cc=neil@brown.name \
--cc=sander@svanheule.net \
--cc=sergio.paracuellos@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 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.