From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: 이왕석 <wangseok.lee@samsung.com>
Cc: "kishon@ti.com" <kishon@ti.com>,
"vkoul@kernel.org" <vkoul@kernel.org>,
"linux-phy@lists.infradead.org" <linux-phy@lists.infradead.org>
Subject: Re: [PATCH] phy: add axis artpec8 pcie phy driver
Date: Fri, 28 Jan 2022 12:17:58 +0100 [thread overview]
Message-ID: <20220128111758.ynftwfc5mnwxcatw@krzk-bin> (raw)
In-Reply-To: <20220128060142epcms2p1d8ad5b735ed3594abdfc3b951fd56d00@epcms2p1>
On Fri, Jan 28, 2022 at 03:01:42PM +0900, 이왕석 wrote:
> add axis artpec8 pcie phy driver
>
> Signed-off-by: wangseok.lee <wangseok.lee@samsung.com>
> ---
> drivers/phy/artpec/Kconfig | 7 +
> drivers/phy/artpec/Makefile | 2 +
> drivers/phy/artpec/phy-artpec8-pcie.c | 880 ++++++++++++++++++++++++++++++++++
> 3 files changed, 889 insertions(+)
> create mode 100644 drivers/phy/artpec/Kconfig
> create mode 100644 drivers/phy/artpec/Makefile
> create mode 100644 drivers/phy/artpec/phy-artpec8-pcie.c
>
> diff --git a/drivers/phy/artpec/Kconfig b/drivers/phy/artpec/Kconfig
> new file mode 100644
> index 0000000..68c5ecb
> --- /dev/null
> +++ b/drivers/phy/artpec/Kconfig
> @@ -0,0 +1,7 @@
> +config PHY_ARTPEC8_PCIE
> + bool "ARTPEC-8 PCIe PHY driver"
> + depends on OF && (ARCH_ARTPEC8 || COMPILE_TEST)
What is ARCH_ARTPEC8?
> + select GENERIC_PHY
> + help
> + Enable PCIe PHY support for ARTPEC-8.
> + This driver provides PHY interface for ARTPEC-8 PCIe controller.
> diff --git a/drivers/phy/artpec/Makefile b/drivers/phy/artpec/Makefile
> new file mode 100644
> index 0000000..45d853c
> --- /dev/null
> +++ b/drivers/phy/artpec/Makefile
> @@ -0,0 +1,2 @@
> +# SPDX-License-Identifier: GPL-2.0
> +obj-$(CONFIG_PHY_ARTPEC8_PCIE) += phy-artpec8-pcie.o
> diff --git a/drivers/phy/artpec/phy-artpec8-pcie.c b/drivers/phy/artpec/phy-artpec8-pcie.c
> new file mode 100644
> index 0000000..1d1f37f
> --- /dev/null
> +++ b/drivers/phy/artpec/phy-artpec8-pcie.c
> @@ -0,0 +1,880 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +/*
> + * PHY provider for ARTPEC-8 PCIe controller
> + *
> + * Copyright (C) 2019 Samsung Electronics Co., Ltd.
> + * http://www.samsung.com
> + *
> + * Author: Jaeho Cho <jaeho79.cho@samsung.com>
> + */
> +
> +#include <linux/clk.h>
> +#include <linux/io.h>
> +#include <linux/init.h>
> +#include <linux/mfd/syscon.h>
> +#include <linux/module.h>
> +#include <linux/of.h>
> +#include <linux/of_address.h>
> +#include <linux/of_platform.h>
> +#include <linux/platform_device.h>
> +#include <linux/phy/phy.h>
> +#include <linux/regmap.h>
> +#include <linux/mfd/samsung-sysmgr.h>
This does not exist. I don't think you compiled it. If that's the case,
such code should not be posted to the mailing list...
One more comment later but in general there is no point in reviewing
unbuildable code.
> +#include <linux/debugfs.h>
> +
> +/* ARTPEC-8 PCIe PHY registers */
> +/* CMN registers */
(...)
> +
> +static const struct phy_ops artpec8_phy_ops = {
> + .init = artpec8_pcie_phy_init,
> + .exit = artpec8_pcie_phy_exit,
> + .reset = artpec8_pcie_phy_reset,
> + .power_on = artpec8_pcie_phy_power_on,
> + .power_off = artpec8_pcie_phy_power_off,
> + .owner = THIS_MODULE,
> +};
> +
> +static const struct artpec8_pcie_phy_data artpec8_pcie_phy_data = {
> + .ops = &artpec8_phy_ops,
> +};
> +
> +static const struct of_device_id artpec8_pcie_phy_match[] = {
> + {
> + .compatible = "samsung,artpec8-pcie-phy",
Where is it documented? Did you run checkpatch?
Best regards,
Krzysztof
> +
> + if (artpec8_phy->soc_pll_clk)
> + clk_disable_unprepare(artpec8_phy->soc_pll_clk);
> +
> + return 0;
> +}
> +
> +static struct platform_driver artpec8_pcie_phy_driver = {
> + .probe = artpec8_pcie_phy_probe,
> + .remove = __exit_p(artpec8_pcie_phy_remove),
> + .driver = {
> + .of_match_table = artpec8_pcie_phy_match,
> + .name = "artpec8_pcie_phy",
> + }
> +};
> +
> +module_platform_driver(artpec8_pcie_phy_driver);
> +
> +MODULE_LICENSE("GPL v2");
> +MODULE_AUTHOR("Jaeho Cho <jaeho79.cho@samsung.com>");
> --
> 2.9.5
>
> --
> linux-phy mailing list
> linux-phy@lists.infradead.org
> https://lists.infradead.org/mailman/listinfo/linux-phy
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2022-01-28 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220128060142epcms2p1d8ad5b735ed3594abdfc3b951fd56d00@epcms2p1>
2022-01-28 6:01 ` [PATCH] phy: add axis artpec8 pcie phy driver 이왕석
2022-01-28 11:17 ` Krzysztof Kozlowski [this message]
[not found] <CGME20220329061427epcms2p1b679df4bcb3b0d1f6d836b73291b2c1d@epcms2p1>
2022-03-29 6:14 ` 이왕석
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=20220128111758.ynftwfc5mnwxcatw@krzk-bin \
--to=krzysztof.kozlowski@canonical.com \
--cc=kishon@ti.com \
--cc=linux-phy@lists.infradead.org \
--cc=vkoul@kernel.org \
--cc=wangseok.lee@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