From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Sriranjani P <sriranjani.p@samsung.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
richardcochran@gmail.com, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, mcoquelin.stm32@gmail.com,
alim.akhtar@samsung.com, linux-fsd@tesla.com,
pankaj.dubey@samsung.com, swathi.ks@samsung.com,
ravi.patel@samsung.com
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Chandrasekar R <rcsekar@samsung.com>,
Suresh Siddha <ssiddha@tesla.com>
Subject: Re: [PATCH v3 2/4] net: stmmac: dwc-qos: Add FSD EQoS support
Date: Mon, 14 Aug 2023 21:50:44 +0200 [thread overview]
Message-ID: <b224ccaf-d70f-8f65-4b2f-6f4798841558@linaro.org> (raw)
In-Reply-To: <20230814112539.70453-3-sriranjani.p@samsung.com>
On 14/08/2023 13:25, Sriranjani P wrote:
> The FSD SoC contains two instance of the Synopsys DWC ethernet QOS IP core.
> The binding that it uses is slightly different from existing ones because
> of the integration (clocks, resets).
>
> For FSD SoC, a mux switch is needed between internal and external clocks.
> By default after reset internal clock is used but for receiving packets
> properly, external clock is needed. Mux switch to external clock happens
> only when the external clock is present.
>
> Signed-off-by: Chandrasekar R <rcsekar@samsung.com>
> Signed-off-by: Suresh Siddha <ssiddha@tesla.com>
> Signed-off-by: Swathi K S <swathi.ks@samsung.com>
> Signed-off-by: Sriranjani P <sriranjani.p@samsung.com>
> ---
> +static int dwc_eqos_setup_rxclock(struct platform_device *pdev, int ins_num)
> +{
> + struct device_node *np = pdev->dev.of_node;
> + struct regmap *syscon;
> + unsigned int reg;
> +
> + if (np && of_property_read_bool(np, "fsd-rx-clock-skew")) {
> + syscon = syscon_regmap_lookup_by_phandle_args(np,
> + "fsd-rx-clock-skew",
> + 1, ®);
> + if (IS_ERR(syscon)) {
> + dev_err(&pdev->dev,
> + "couldn't get the rx-clock-skew syscon!\n");
> + return PTR_ERR(syscon);
> + }
> +
> + regmap_write(syscon, reg, rx_clock_skew_val[ins_num]);
> + }
> +
> + return 0;
> +}
> +
> +static int fsd_eqos_clk_init(struct fsd_eqos_plat_data *plat,
> + struct plat_stmmacenet_data *data)
> +{
> + int ret = 0, i;
> +
> + const struct fsd_eqos_variant *fsd_eqos_v_data =
> + plat->fsd_eqos_inst_var;
> +
> + plat->clks = devm_kcalloc(plat->dev, fsd_eqos_v_data->num_clks,
> + sizeof(*plat->clks), GFP_KERNEL);
> + if (!plat->clks)
> + return -ENOMEM;
> +
> + for (i = 0; i < fsd_eqos_v_data->num_clks; i++)
> + plat->clks[i].id = fsd_eqos_v_data->clk_list[i];
> +
> + ret = devm_clk_bulk_get(plat->dev, fsd_eqos_v_data->num_clks,
> + plat->clks);
Instead of duplicating entire clock management with existing code, you
should extend/rework existing one.
This code is unfortunately great example how not to stuff vendor code
into upstream project. :(
> +
> + return ret;
> +}
> +
> +static int fsd_clks_endisable(void *priv, bool enabled)
> +{
> + int ret, num_clks;
> + struct fsd_eqos_plat_data *plat = priv;
> +
> + num_clks = plat->fsd_eqos_inst_var->num_clks;
> +
> + if (enabled) {
> + ret = clk_bulk_prepare_enable(num_clks, plat->clks);
> + if (ret) {
> + dev_err(plat->dev, "Clock enable failed, err = %d\n", ret);
> + return ret;
> + }
> + } else {
> + clk_bulk_disable_unprepare(num_clks, plat->clks);
> + }
> +
> + return 0;
> +}
> +
> +static int fsd_eqos_probe(struct platform_device *pdev,
> + struct plat_stmmacenet_data *data,
> + struct stmmac_resources *res)
> +{
> + struct fsd_eqos_plat_data *priv_plat;
> + struct device_node *np = pdev->dev.of_node;
> + int ret = 0;
> +
> + priv_plat = devm_kzalloc(&pdev->dev, sizeof(*priv_plat), GFP_KERNEL);
> + if (!priv_plat) {
> + ret = -ENOMEM;
return -ENOMEM
> + goto error;
> + }
> +
> + priv_plat->dev = &pdev->dev;
> + data->bus_id = of_alias_get_id(np, "eth");
No, you cannot do like this. Aliases are board specific and are based on
labeling on the board.
> +
> + priv_plat->fsd_eqos_inst_var = &fsd_eqos_clk_info[data->bus_id];
> +
> + ret = fsd_eqos_clk_init(priv_plat, data);
> +
> + data->bsp_priv = priv_plat;
> + data->clks_config = fsd_clks_endisable;
> + data->rxmux_setup = dwc_eqos_rxmux_setup;
> +
> + ret = fsd_clks_endisable(priv_plat, true);
> + if (ret)
> + goto error;
> +
> + ret = dwc_eqos_setup_rxclock(pdev, data->bus_id);
> + if (ret) {
> + fsd_clks_endisable(priv_plat, false);
> + dev_err_probe(&pdev->dev, ret, "Unable to setup rxclock\n");
The syntax is: return dev_err_probe().
> + }
> +
> +error:
> + return ret;
> +}
....
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-08-14 19:51 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230814112600epcas5p49fe29a3ef85e2b0158f5ee3426652fc8@epcas5p4.samsung.com>
2023-08-14 11:25 ` [PATCH v3 0/4] " Sriranjani P
[not found] ` <CGME20230814112605epcas5p31aca7b23e70e8d93df11414291f7ce66@epcas5p3.samsung.com>
2023-08-14 11:25 ` [PATCH v3 1/4] dt-bindings: net: Add FSD EQoS device tree bindings Sriranjani P
2023-08-14 13:33 ` Rob Herring
2023-08-16 5:36 ` Sriranjani P
2023-08-16 5:40 ` Krzysztof Kozlowski
2023-08-17 14:54 ` Rob Herring
2023-08-14 19:39 ` Krzysztof Kozlowski
2023-08-16 5:58 ` Sriranjani P
2023-08-16 6:18 ` Krzysztof Kozlowski
2024-06-06 9:14 ` Swathi K S
2023-08-14 20:39 ` Andrew Lunn
2024-06-06 9:14 ` Swathi K S
2024-06-06 13:25 ` Andrew Lunn
2024-07-29 8:47 ` Swathi K S
[not found] ` <CGME20230814112612epcas5p275cffb4d3dae86c6090ca246083631c4@epcas5p2.samsung.com>
2023-08-14 11:25 ` [PATCH v3 2/4] net: stmmac: dwc-qos: Add FSD EQoS support Sriranjani P
2023-08-14 19:50 ` Krzysztof Kozlowski [this message]
2023-08-16 6:38 ` Sriranjani P
2023-08-18 9:27 ` Krzysztof Kozlowski
2024-06-06 9:14 ` Swathi K S
2024-06-06 12:16 ` Krzysztof Kozlowski
2023-08-14 20:47 ` Andrew Lunn
2024-06-06 9:16 ` Swathi K S
[not found] ` <CGME20230814112617epcas5p1bc094e9cf29da5dd7d1706e3f509ac28@epcas5p1.samsung.com>
2023-08-14 11:25 ` [PATCH v3 3/4] arm64: dts: fsd: Add Ethernet support for FSYS0 Block of FSD SoC Sriranjani P
2023-08-14 19:40 ` Krzysztof Kozlowski
2023-08-14 19:56 ` Krzysztof Kozlowski
2023-08-16 6:40 ` Sriranjani P
2023-08-14 20:50 ` Andrew Lunn
2024-06-06 9:14 ` Swathi K S
2024-06-06 13:22 ` Andrew Lunn
2024-07-29 8:49 ` Swathi K S
2023-08-14 20:51 ` Andrew Lunn
[not found] ` <CGME20230814112625epcas5p1e1d488a590bfc10d4e2a06dcff166037@epcas5p1.samsung.com>
2023-08-14 11:25 ` [PATCH v3 4/4] arm64: dts: fsd: Add Ethernet support for PERIC " Sriranjani P
2023-08-14 19:41 ` Krzysztof Kozlowski
2023-08-14 19:41 ` Krzysztof Kozlowski
2023-08-16 6:26 ` Sriranjani P
2023-08-14 20:53 ` Andrew Lunn
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=b224ccaf-d70f-8f65-4b2f-6f4798841558@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alexandre.torgue@foss.st.com \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsd@tesla.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pankaj.dubey@samsung.com \
--cc=ravi.patel@samsung.com \
--cc=rcsekar@samsung.com \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sriranjani.p@samsung.com \
--cc=ssiddha@tesla.com \
--cc=swathi.ks@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®