[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.9999.1906170252410.19994@viisi.sifive.com>
Date: Mon, 17 Jun 2019 02:58:20 -0700 (PDT)
From: Paul Walmsley <paul.walmsley@...ive.com>
To: Yash Shah <yash.shah@...ive.com>
cc: Andreas Schwab <schwab@...e.de>, davem@...emloft.net,
devicetree@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org,
robh+dt@...nel.org, mark.rutland@....com,
nicolas.ferre@...rochip.com, palmer@...ive.com,
aou@...s.berkeley.edu, ynezz@...e.cz, sachin.ghadi@...ive.com
Subject: Re: [PATCH v2 0/2] Add macb support for SiFive FU540-C000
Hi Yash,
On Mon, 17 Jun 2019, Andreas Schwab wrote:
> On Jun 17 2019, Yash Shah <yash.shah@...ive.com> wrote:
>
> > - Add "MACB_SIFIVE_FU540" in Kconfig to support SiFive FU540 in macb
> > driver. This is needed because on FU540, the macb driver depends on
> > SiFive GPIO driver.
>
> This of course requires that the GPIO driver is upstreamed first.
What's the impact of enabling CONFIG_MACB_SIFIVE_FU540 when the GPIO
driver isn't present? (After modifying the Kconfig "depends" line
appropriately.)
Looks to me that it shouldn't have an impact unless the DT string is
present, and even then, the impact might simply be that the MACB driver
may not work?
- Paul
Powered by blists - more mailing lists