All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: "Arınç ÜNAL" <arinc.unal@arinc9.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 09:35:50 +0100	[thread overview]
Message-ID: <CAMhs-H-74bK3m975Dtmg2zPrGjmqzSd+Tb_qdUV14yJBAWRQbw@mail.gmail.com> (raw)
In-Reply-To: <20220215081725.3463-2-arinc.unal@arinc9.com>

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,
    Sergio Paracuellos

  reply	other threads:[~2022-02-15  8:36 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 [this message]
2022-02-15  8:49     ` Arınç ÜNAL
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=CAMhs-H-74bK3m975Dtmg2zPrGjmqzSd+Tb_qdUV14yJBAWRQbw@mail.gmail.com \
    --to=sergio.paracuellos@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=arinc.unal@arinc9.com \
    --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 \
    /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.