From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH] net: dwc_eth_qos: add Kconfig option to select supported configuration
Date: Wed, 10 Jun 2020 14:10:19 -0400 [thread overview]
Message-ID: <20200610181019.GE24893@bill-the-cat> (raw)
In-Reply-To: <20200608092719.10643-1-patrick.delaunay@st.com>
On Mon, Jun 08, 2020 at 11:27:19AM +0200, Patrick Delaunay wrote:
> Add configuration flag to select the supported dwc driver configuration:
> - CONFIG_DWC_ETH_QOS_TEGRA186
> - CONFIG_DWC_ETH_QOS_IMX
> - CONFIG_DWC_ETH_QOS_STM32
>
> See Linux driver ethernet/stmicro/stmmac and associated glue layers
> for other configuration examples.
>
> This patch removes the not-selected compatibles and lets the linker remove
> the unused functions to reduce the size of the driver.
>
> Signed-off-by: Patrick Delaunay <patrick.delaunay@st.com>
> ---
> Hi,
>
> I propose this patch after Marek's remark in [1].
>
> It is also linked to [2] to limit the STM32 glue for ST compatible.
>
> [1] net: dwc_eth_qos: Make clk_rx and clk_tx optional
> http://patchwork.ozlabs.org/project/uboot/patch/20200512095603.29126-5-david.wu at rock-chips.com/#2432595
>
> [2] net: dwc_eth_qos: update the compatible supported for STM32
> http://patchwork.ozlabs.org/project/uboot/list/?series=176917
>
>
> drivers/net/Kconfig | 27 ++++++++++++++++++++++++---
> drivers/net/dwc_eth_qos.c | 12 +++++++++---
> 2 files changed, 33 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig
> index 0b08de0ef4..c4b3667d3b 100644
> --- a/drivers/net/Kconfig
> +++ b/drivers/net/Kconfig
> @@ -156,9 +156,30 @@ config DWC_ETH_QOS
> help
> This driver supports the Synopsys Designware Ethernet QOS (Quality
> Of Service) IP block. The IP supports many options for bus type,
> - clocking/reset structure, and feature list. This driver currently
> - supports the specific configuration used in NVIDIA's Tegra186 chip,
> - but should be extensible to other combinations quite easily.
> + clocking/reset structure, and feature list.
> +
> +config DWC_ETH_QOS_IMX
> + bool "Synopsys DWC Ethernet QOS device support for IMX"
> + depends on DWC_ETH_QOS
> + help
> + The Synopsys Designware Ethernet QOS IP block with the specific
> + configuration used in IMX soc.
> +
> +config DWC_ETH_QOS_STM32
> + bool "Synopsys DWC Ethernet QOS device support for STM32"
> + depends on DWC_ETH_QOS
> + default y if ARCH_STM32MP
> + help
> + The Synopsys Designware Ethernet QOS IP block with the specific
> + configuration used in STM32MP soc.
> +
> +config DWC_ETH_QOS_TEGRA186
> + bool "Synopsys DWC Ethernet QOS device support for TEGRA186"
> + depends on DWC_ETH_QOS
> + default y if TEGRA186
> + help
> + The Synopsys Designware Ethernet QOS IP block with specific
> + configuration used in NVIDIA's Tegra186 chip.
>
> config E1000
> bool "Intel PRO/1000 Gigabit Ethernet support"
I like this idea. But, is there a reason to have more than one of these
enabled? Assuming not, we should do this as a choice I think so it'll
be clear to the next SoC that they'll need to add this table right away.
Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200610/1161f393/attachment.sig>
next prev parent reply other threads:[~2020-06-10 18:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 9:27 [PATCH] net: dwc_eth_qos: add Kconfig option to select supported configuration Patrick Delaunay
2020-06-10 18:10 ` Tom Rini [this message]
2020-06-10 18:42 ` Marek Vasut
2020-06-10 18:52 ` Tom Rini
2020-06-10 18:55 ` Marek Vasut
2020-06-10 18:58 ` Tom Rini
2020-06-10 19:01 ` Marek Vasut
2020-06-10 20:11 ` Tom Rini
2020-06-10 20:46 ` Marek Vasut
2020-06-10 20:54 ` Tom Rini
2020-06-10 20:56 ` Marek Vasut
2020-06-10 21:35 ` Tom Rini
2020-06-10 21:40 ` Marek Vasut
2020-06-10 21:57 ` Tom Rini
2020-06-10 22:02 ` Marek Vasut
2020-06-10 22:17 ` Tom Rini
2020-06-10 22:32 ` Marek Vasut
2020-06-11 13:44 ` Patrick DELAUNAY
2020-06-11 16:42 ` Marek Vasut
2020-08-05 20:26 ` 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=20200610181019.GE24893@bill-the-cat \
--to=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox