All of lore.kernel.org
 help / color / mirror / Atom feed
From: "André Przywara" <andre.przywara@arm.com>
To: u-boot@lists.denx.de
Subject: [PATCH v1 5/7] arm: dts: s700: add node for ethernet controller
Date: Tue, 12 May 2020 17:39:46 +0100	[thread overview]
Message-ID: <84270c79-ad0f-872d-d4bc-8a7d52598c99@arm.com> (raw)
In-Reply-To: <20200512150903.GC12564@bill-the-cat>

On 12/05/2020 16:09, Tom Rini wrote:

Hi,

> On Tue, May 12, 2020 at 03:53:55PM +0100, Andr? Przywara wrote:
>> On 12/05/2020 15:25, Tom Rini wrote:
>>> On Tue, May 12, 2020 at 03:18:33PM +0100, Andr? Przywara wrote:
>>>> On 09/05/2020 15:25, Amit Singh Tomar wrote:
>>>>> This patch adds node for ethernet controller found on Action Semi OWL
>>>>> S700 SoC.
>>>>>
>>>>> Since, there is no upstream Linux binding exist for S700 ethernet
>>>>> controller, Changes are put in u-boot specific dtsi file.
>>>>
>>>> But that should not be the S700 SoC .dtsi, instead the cubieboard .dts
>>>> file, since you specify the PHY mode in here (which is board specific).
>>>
>>> The general way to move forward here is that bindings should be getting
>>> proposed to Linux and accepted there, and U-Boot can take a WIP of them,
>>> that gets updated later on to match, but we shouldn't get it here first.
>>
>> Yes, this is of course a stop-gap measure, but a useful one: Being able
>> to TFTP a kernel helps with developing the kernel port, especially since
>> U-Boot doesn't support MMC (yet).
>> And there are easier things than pushing a DT binding into the kernel
>> tree without having a Linux driver ready ...
> 
> So, we're at -rc2 for v2020.07.  The DDR calculation stuff I can see
> getting pulled in.  Is the ethernet driver for this SoC so far from done
> that it's not ready for linux-next?  Things don't have to be in mainline
> proper, but the expectation is that it's making reasonable progress
> there and been reviewed so that binding changes between what we take in
> U-Boot at first and a final re-sync once it is in mainline are minimal.

I don't think there is any particular rush in getting this actually
merged. After all it seems like the users of this board can be counted
on one hand.
I think it's nice to have this on the list, so interested parties can
pull it in if there is a need. But we can surely wait how the binding
evolves in the kernel tree, though this might take some time.

Cheers,
Andre.

  parent reply	other threads:[~2020-05-12 16:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09 14:25 [PATCH v1 0/7] add Ethernet support for S700 Amit Singh Tomar
2020-05-09 14:25 ` [PATCH v1 1/7] clk: actions: Add Ethernet clocks Amit Singh Tomar
2020-07-08  3:02   ` Tom Rini
2020-05-09 14:25 ` [PATCH v1 2/7] net: phy: realtek: Add support for RTL8201F PHY module Amit Singh Tomar
2020-07-08  3:02   ` Tom Rini
2020-05-09 14:25 ` [PATCH v1 3/7] net: phy: realtek: Introduce PHY_RTL8201F_S700_RMII_TIMINGS to adjust rx/tx timings Amit Singh Tomar
2020-07-08  3:02   ` Tom Rini
2020-05-09 14:25 ` [PATCH v1 4/7] net: designware: s700: Add glue code for S700 mac Amit Singh Tomar
2020-07-08  3:03   ` Tom Rini
2020-05-09 14:25 ` [PATCH v1 5/7] arm: dts: s700: add node for ethernet controller Amit Singh Tomar
2020-05-12 14:18   ` André Przywara
2020-05-12 14:25     ` Tom Rini
2020-05-12 14:42       ` Amit Tomer
2020-05-12 14:53         ` Tom Rini
2020-05-12 14:53       ` André Przywara
2020-05-12 15:09         ` Tom Rini
2020-05-12 16:14           ` Amit Tomer
2020-05-12 16:39           ` André Przywara [this message]
2020-05-12 19:59             ` Tom Rini
2020-05-12 14:37     ` Amit Tomer
2020-05-12 14:56       ` André Przywara
2020-07-08  3:03   ` Tom Rini
2020-05-09 14:25 ` [PATCH v1 6/7] owl: Kconfig: Enable DM eth for OWL platform Amit Singh Tomar
2020-07-08  3:03   ` Tom Rini
2020-05-09 14:25 ` [PATCH v1 7/7] configs: Enable mac and phy configs Amit Singh Tomar
2020-07-08  3:03   ` Tom Rini

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=84270c79-ad0f-872d-d4bc-8a7d52598c99@arm.com \
    --to=andre.przywara@arm.com \
    --cc=u-boot@lists.denx.de \
    /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.