From: Vivek Gautam <gautamvivek1987@gmail.com> To: Kishon Vijay Abraham I <kishon@ti.com> Cc: Linux USB Mailing List <linux-usb@vger.kernel.org>, "linux-samsung-soc@vger.kernel.org" <linux-samsung-soc@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, linux-doc@vger.kernel.org, Greg KH <gregkh@linuxfoundation.org>, Felipe Balbi <balbi@ti.com>, Kukjin Kim <kgene.kim@samsung.com>, Tomasz Figa <t.figa@samsung.com>, Kamil Debski <k.debski@samsung.com>, Jingoo Han <jg1.han@samsung.com>, Sylwester Nawrocki <sylvester.nawrocki@gmail.com> Subject: Re: [PATCH V4 1/5] phy: Add new Exynos5 USB 3.0 PHY driver Date: Mon, 14 Apr 2014 18:50:48 +0530 [thread overview] Message-ID: <CAFp+6iFFW8XQg_UtYEZfaiENULZDD8A7_9fr4f2no=qfau7-sQ@mail.gmail.com> (raw) In-Reply-To: <534BDBBC.5010701@ti.com> On Mon, Apr 14, 2014 at 6:29 PM, Kishon Vijay Abraham I <kishon@ti.com> wrote: > > > On Monday 14 April 2014 06:12 PM, Vivek Gautam wrote: >> Hi, >> >> >> On Mon, Apr 14, 2014 at 5:57 PM, Kishon Vijay Abraham I <kishon@ti.com> wrote: >>> Hi, >>> >>> On Tuesday 08 April 2014 08:06 PM, Vivek Gautam wrote: >>>> Add a new driver for the USB 3.0 PHY on Exynos5 series of SoCs. >>>> The new driver uses the generic PHY framework and will interact >>>> with DWC3 controller present on Exynos5 series of SoCs. >>>> Thereby, removing old phy-samsung-usb3 driver and related code >>>> used untill now which was based on usb/phy framework. >>>> >>>> Signed-off-by: Vivek Gautam <gautam.vivek@samsung.com> >>>> --- >>>> .../devicetree/bindings/phy/samsung-phy.txt | 42 ++ >>>> drivers/phy/Kconfig | 11 + >>>> drivers/phy/Makefile | 1 + >>>> drivers/phy/phy-exynos5-usbdrd.c | 668 ++++++++++++++++++++ >>>> 4 files changed, 722 insertions(+) >>>> create mode 100644 drivers/phy/phy-exynos5-usbdrd.c >>>> >>>> diff --git a/Documentation/devicetree/bindings/phy/samsung-phy.txt b/Documentation/devicetree/bindings/phy/samsung-phy.txt >>>> index 28f9edb..6d99ba9 100644 >>>> --- a/Documentation/devicetree/bindings/phy/samsung-phy.txt >>>> +++ b/Documentation/devicetree/bindings/phy/samsung-phy.txt >>>> @@ -74,3 +74,45 @@ phy-consumer@12340000 { >>>> >>>> Refer to DT bindings documentation of particular PHY consumer devices for more >>>> information about required PHYs and the way of specification. >>>> + >>>> +Samsung Exynos5 SoC series USB DRD PHY controller >>>> +-------------------------------------------------- >>>> + >>>> +Required properties: >>>> +- compatible : Should be set to one of the following supported values: >>>> + - "samsung,exynos5250-usbdrd-phy" - for exynos5250 SoC, >>>> + - "samsung,exynos5420-usbdrd-phy" - for exynos5420 SoC. >>>> +- reg : Register offset and length of USB DRD PHY register set; >>>> +- clocks: Clock IDs array as required by the controller >>>> +- clock-names: names of clocks correseponding to IDs in the clock property; >>>> + Required clocks: >>>> + - phy: main PHY clock (same as USB DRD controller i.e. DWC3 IP clock), >>>> + used for register access. >>>> + - ref: PHY's reference clock (usually crystal clock), associated by >>>> + phy name, used to determine bit values for clock settings >>>> + register. >>>> + Additional clock required for Exynos5420: >>>> + - usb30_sclk_100m: Additional special clock used for PHY operation >>>> + depicted as 'sclk_usbphy30' in CMU of Exynos5420. >>>> +- samsung,syscon-phandle: phandle for syscon interface, which is used to >>>> + control pmu registers for power isolation. >>>> +- samsung,pmu-offset: phy power control register offset to pmu-system-controller >>>> + base. >>>> +- #phy-cells : from the generic PHY bindings, must be 1; >>>> + >>>> +For "samsung,exynos5250-usbdrd-phy" and "samsung,exynos5420-usbdrd-phy" >>>> +compatible PHYs, the second cell in the PHY specifier identifies the >>>> +PHY id, which is interpreted as follows: >>>> + 0 - UTMI+ type phy, >>>> + 1 - PIPE3 type phy, >>>> + >>>> +Example: >>>> + usb3_phy: usbphy@12100000 { >>>> + compatible = "samsung,exynos5250-usbdrd-phy"; >>>> + reg = <0x12100000 0x100>; >>>> + clocks = <&clock 286>, <&clock 1>; >>>> + clock-names = "phy", "usb3phy_refclk"; >>>> + samsung,syscon-phandle = <&pmu_syscon>; >>>> + samsung,pmu-offset = <0x704>; >>>> + #phy-cells = <1>; >>>> + }; >>>> diff --git a/drivers/phy/Kconfig b/drivers/phy/Kconfig >>>> index 8d3c49c..d955a05 100644 >>>> --- a/drivers/phy/Kconfig >>>> +++ b/drivers/phy/Kconfig >>>> @@ -166,4 +166,15 @@ config PHY_XGENE >>>> help >>>> This option enables support for APM X-Gene SoC multi-purpose PHY. >>>> >>>> +config PHY_EXYNOS5_USBDRD >>>> + tristate "Exynos5 SoC series USB DRD PHY driver" >>>> + depends on ARCH_EXYNOS5 && OF >>>> + depends on HAS_IOMEM >>>> + select GENERIC_PHY >>>> + select MFD_SYSCON >>> >>> Lets try to avoid select in Kconfig. We've got enough problems with that. >> >> I hope you meant with "select MFD_SYSCON". >> We are referencing the syscon for accessing pmu reg, for which we need >> this config to be selected. >> Other Exynos phy drivers also need this config and for that they have >> selected this. >> >> Do you want me to do it any other way ? > > depends on is one option. Ok, i can see there are places where depends_on MFD_SYSCON is used. "drivers/gpu/drm/exynos/Kconfig:60" so, do you want me to fix at other places too ? But i also have a question here. MFD_SYSCON is a subsystem that's facilitating us in getting our work done here by giving an access to pmu_system_controller. So unless MFD_SYSCON is exposed, the phy driver will not be exposed to us. So is that valid enough really ? > > Thanks > Kishon > -- > To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Best Regards Vivek Gautam Samsung R&D Institute, Bangalore India
WARNING: multiple messages have this Message-ID (diff)
From: gautamvivek1987@gmail.com (Vivek Gautam) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH V4 1/5] phy: Add new Exynos5 USB 3.0 PHY driver Date: Mon, 14 Apr 2014 18:50:48 +0530 [thread overview] Message-ID: <CAFp+6iFFW8XQg_UtYEZfaiENULZDD8A7_9fr4f2no=qfau7-sQ@mail.gmail.com> (raw) In-Reply-To: <534BDBBC.5010701@ti.com> On Mon, Apr 14, 2014 at 6:29 PM, Kishon Vijay Abraham I <kishon@ti.com> wrote: > > > On Monday 14 April 2014 06:12 PM, Vivek Gautam wrote: >> Hi, >> >> >> On Mon, Apr 14, 2014 at 5:57 PM, Kishon Vijay Abraham I <kishon@ti.com> wrote: >>> Hi, >>> >>> On Tuesday 08 April 2014 08:06 PM, Vivek Gautam wrote: >>>> Add a new driver for the USB 3.0 PHY on Exynos5 series of SoCs. >>>> The new driver uses the generic PHY framework and will interact >>>> with DWC3 controller present on Exynos5 series of SoCs. >>>> Thereby, removing old phy-samsung-usb3 driver and related code >>>> used untill now which was based on usb/phy framework. >>>> >>>> Signed-off-by: Vivek Gautam <gautam.vivek@samsung.com> >>>> --- >>>> .../devicetree/bindings/phy/samsung-phy.txt | 42 ++ >>>> drivers/phy/Kconfig | 11 + >>>> drivers/phy/Makefile | 1 + >>>> drivers/phy/phy-exynos5-usbdrd.c | 668 ++++++++++++++++++++ >>>> 4 files changed, 722 insertions(+) >>>> create mode 100644 drivers/phy/phy-exynos5-usbdrd.c >>>> >>>> diff --git a/Documentation/devicetree/bindings/phy/samsung-phy.txt b/Documentation/devicetree/bindings/phy/samsung-phy.txt >>>> index 28f9edb..6d99ba9 100644 >>>> --- a/Documentation/devicetree/bindings/phy/samsung-phy.txt >>>> +++ b/Documentation/devicetree/bindings/phy/samsung-phy.txt >>>> @@ -74,3 +74,45 @@ phy-consumer at 12340000 { >>>> >>>> Refer to DT bindings documentation of particular PHY consumer devices for more >>>> information about required PHYs and the way of specification. >>>> + >>>> +Samsung Exynos5 SoC series USB DRD PHY controller >>>> +-------------------------------------------------- >>>> + >>>> +Required properties: >>>> +- compatible : Should be set to one of the following supported values: >>>> + - "samsung,exynos5250-usbdrd-phy" - for exynos5250 SoC, >>>> + - "samsung,exynos5420-usbdrd-phy" - for exynos5420 SoC. >>>> +- reg : Register offset and length of USB DRD PHY register set; >>>> +- clocks: Clock IDs array as required by the controller >>>> +- clock-names: names of clocks correseponding to IDs in the clock property; >>>> + Required clocks: >>>> + - phy: main PHY clock (same as USB DRD controller i.e. DWC3 IP clock), >>>> + used for register access. >>>> + - ref: PHY's reference clock (usually crystal clock), associated by >>>> + phy name, used to determine bit values for clock settings >>>> + register. >>>> + Additional clock required for Exynos5420: >>>> + - usb30_sclk_100m: Additional special clock used for PHY operation >>>> + depicted as 'sclk_usbphy30' in CMU of Exynos5420. >>>> +- samsung,syscon-phandle: phandle for syscon interface, which is used to >>>> + control pmu registers for power isolation. >>>> +- samsung,pmu-offset: phy power control register offset to pmu-system-controller >>>> + base. >>>> +- #phy-cells : from the generic PHY bindings, must be 1; >>>> + >>>> +For "samsung,exynos5250-usbdrd-phy" and "samsung,exynos5420-usbdrd-phy" >>>> +compatible PHYs, the second cell in the PHY specifier identifies the >>>> +PHY id, which is interpreted as follows: >>>> + 0 - UTMI+ type phy, >>>> + 1 - PIPE3 type phy, >>>> + >>>> +Example: >>>> + usb3_phy: usbphy at 12100000 { >>>> + compatible = "samsung,exynos5250-usbdrd-phy"; >>>> + reg = <0x12100000 0x100>; >>>> + clocks = <&clock 286>, <&clock 1>; >>>> + clock-names = "phy", "usb3phy_refclk"; >>>> + samsung,syscon-phandle = <&pmu_syscon>; >>>> + samsung,pmu-offset = <0x704>; >>>> + #phy-cells = <1>; >>>> + }; >>>> diff --git a/drivers/phy/Kconfig b/drivers/phy/Kconfig >>>> index 8d3c49c..d955a05 100644 >>>> --- a/drivers/phy/Kconfig >>>> +++ b/drivers/phy/Kconfig >>>> @@ -166,4 +166,15 @@ config PHY_XGENE >>>> help >>>> This option enables support for APM X-Gene SoC multi-purpose PHY. >>>> >>>> +config PHY_EXYNOS5_USBDRD >>>> + tristate "Exynos5 SoC series USB DRD PHY driver" >>>> + depends on ARCH_EXYNOS5 && OF >>>> + depends on HAS_IOMEM >>>> + select GENERIC_PHY >>>> + select MFD_SYSCON >>> >>> Lets try to avoid select in Kconfig. We've got enough problems with that. >> >> I hope you meant with "select MFD_SYSCON". >> We are referencing the syscon for accessing pmu reg, for which we need >> this config to be selected. >> Other Exynos phy drivers also need this config and for that they have >> selected this. >> >> Do you want me to do it any other way ? > > depends on is one option. Ok, i can see there are places where depends_on MFD_SYSCON is used. "drivers/gpu/drm/exynos/Kconfig:60" so, do you want me to fix at other places too ? But i also have a question here. MFD_SYSCON is a subsystem that's facilitating us in getting our work done here by giving an access to pmu_system_controller. So unless MFD_SYSCON is exposed, the phy driver will not be exposed to us. So is that valid enough really ? > > Thanks > Kishon > -- > To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in > the body of a message to majordomo at vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Best Regards Vivek Gautam Samsung R&D Institute, Bangalore India
next prev parent reply other threads:[~2014-04-14 13:20 UTC|newest] Thread overview: 119+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-08 14:36 [PATCH V4 0/5] Add Exynos5 USB 3.0 phy driver based on generic PHY framework Vivek Gautam 2014-04-08 14:36 ` Vivek Gautam 2014-04-08 14:36 ` [PATCH V4 1/5] phy: Add new Exynos5 USB 3.0 PHY driver Vivek Gautam 2014-04-08 14:36 ` Vivek Gautam 2014-04-08 14:36 ` Vivek Gautam 2014-04-09 11:06 ` Tomasz Figa 2014-04-09 11:06 ` Tomasz Figa 2014-04-09 11:06 ` Tomasz Figa 2014-04-09 11:49 ` Vivek Gautam 2014-04-09 11:49 ` Vivek Gautam 2014-04-09 11:49 ` Vivek Gautam 2014-04-09 13:33 ` Tomasz Figa 2014-04-09 13:33 ` Tomasz Figa 2014-04-09 13:33 ` Tomasz Figa 2014-04-10 11:39 ` Vivek Gautam 2014-04-10 11:39 ` Vivek Gautam 2014-04-10 11:39 ` Vivek Gautam 2014-04-15 6:09 ` Vivek Gautam 2014-04-15 6:09 ` Vivek Gautam 2014-04-15 6:09 ` Vivek Gautam 2014-04-16 13:44 ` Tomasz Figa 2014-04-16 13:44 ` Tomasz Figa 2014-04-16 13:44 ` Tomasz Figa 2014-04-16 14:49 ` Vivek Gautam 2014-04-16 14:49 ` Vivek Gautam 2014-04-16 14:49 ` Vivek Gautam 2014-04-22 2:18 ` Jingoo Han 2014-04-22 2:18 ` Jingoo Han 2014-04-22 3:35 ` Vivek Gautam 2014-04-22 3:35 ` Vivek Gautam 2014-04-22 3:35 ` Vivek Gautam 2014-04-14 11:54 ` Kishon Vijay Abraham I 2014-04-14 11:54 ` Kishon Vijay Abraham I 2014-04-14 11:54 ` Kishon Vijay Abraham I 2014-04-14 12:05 ` Vivek Gautam 2014-04-14 12:05 ` Vivek Gautam 2014-04-14 12:05 ` Vivek Gautam 2014-04-14 13:05 ` Kishon Vijay Abraham I 2014-04-14 13:05 ` Kishon Vijay Abraham I 2014-04-14 13:05 ` Kishon Vijay Abraham I 2014-04-14 13:44 ` Tomasz Figa 2014-04-14 13:44 ` Tomasz Figa 2014-04-14 13:44 ` Tomasz Figa 2014-04-14 13:49 ` Vivek Gautam 2014-04-14 13:49 ` Vivek Gautam 2014-04-14 13:49 ` Vivek Gautam 2014-04-14 14:21 ` Sylwester Nawrocki 2014-04-14 14:21 ` Sylwester Nawrocki 2014-04-14 14:21 ` Sylwester Nawrocki 2014-04-15 5:07 ` Vivek Gautam 2014-04-15 5:07 ` Vivek Gautam 2014-04-15 5:07 ` Vivek Gautam 2014-04-14 12:27 ` Kishon Vijay Abraham I 2014-04-14 12:27 ` Kishon Vijay Abraham I 2014-04-14 12:27 ` Kishon Vijay Abraham I 2014-04-14 12:42 ` Vivek Gautam 2014-04-14 12:42 ` Vivek Gautam 2014-04-14 12:42 ` Vivek Gautam 2014-04-14 12:59 ` Kishon Vijay Abraham I 2014-04-14 12:59 ` Kishon Vijay Abraham I 2014-04-14 12:59 ` Kishon Vijay Abraham I 2014-04-14 13:20 ` Vivek Gautam [this message] 2014-04-14 13:20 ` Vivek Gautam 2014-04-14 13:20 ` Vivek Gautam 2014-04-14 13:26 ` Kishon Vijay Abraham I 2014-04-14 13:26 ` Kishon Vijay Abraham I 2014-04-14 13:26 ` Kishon Vijay Abraham I 2014-04-14 13:40 ` Vivek Gautam 2014-04-14 13:40 ` Vivek Gautam 2014-04-14 13:40 ` Vivek Gautam 2014-04-14 13:46 ` Vivek Gautam 2014-04-14 13:46 ` Vivek Gautam 2014-04-14 13:46 ` Vivek Gautam 2014-04-14 13:49 ` Tomasz Figa 2014-04-14 13:49 ` Tomasz Figa 2014-04-14 13:49 ` Tomasz Figa 2014-04-15 13:59 ` Kishon Vijay Abraham I 2014-04-15 13:59 ` Kishon Vijay Abraham I 2014-04-15 13:59 ` Kishon Vijay Abraham I 2014-04-14 14:37 ` Sylwester Nawrocki 2014-04-14 14:37 ` Sylwester Nawrocki 2014-04-15 5:09 ` Vivek Gautam 2014-04-15 5:09 ` Vivek Gautam 2014-04-15 5:09 ` Vivek Gautam 2014-04-25 7:57 ` Tushar Behera 2014-04-25 7:57 ` Tushar Behera 2014-04-25 7:57 ` Tushar Behera 2014-04-25 8:08 ` Vivek Gautam 2014-04-25 8:08 ` Vivek Gautam 2014-04-25 8:08 ` Vivek Gautam 2014-04-08 14:36 ` [PATCH v4 2/5] dt: exynos5420: Enable support for USB 3.0 PHY controller Vivek Gautam 2014-04-08 14:36 ` Vivek Gautam 2014-04-08 14:36 ` Vivek Gautam 2014-04-09 11:10 ` Tomasz Figa 2014-04-09 11:10 ` Tomasz Figa 2014-04-09 11:10 ` Tomasz Figa 2014-04-08 14:36 ` [PATCH V4 3/5] dt: exynos5420: Enable support for DWC3 controller Vivek Gautam 2014-04-08 14:36 ` Vivek Gautam 2014-04-08 14:36 ` Vivek Gautam 2014-04-09 11:11 ` Tomasz Figa 2014-04-09 11:11 ` Tomasz Figa 2014-04-08 14:36 ` [PATCH V4 4/5] dt: exynos5250: Enable support for generic USB DRD phy Vivek Gautam 2014-04-08 14:36 ` Vivek Gautam 2014-04-09 11:11 ` Tomasz Figa 2014-04-09 11:11 ` Tomasz Figa 2014-04-09 11:11 ` Tomasz Figa 2014-04-08 14:36 ` [PATCH V4 5/5] usb-phy: samsung-usb3: Remove older phy-samsung-usb3 driver Vivek Gautam 2014-04-08 14:36 ` Vivek Gautam 2014-04-09 11:13 ` Tomasz Figa 2014-04-09 11:13 ` Tomasz Figa 2014-04-09 11:34 ` Vivek Gautam 2014-04-09 11:34 ` Vivek Gautam 2014-04-09 11:34 ` Vivek Gautam 2014-04-16 13:33 ` Richard Genoud 2014-04-16 13:33 ` Richard Genoud 2014-04-16 13:33 ` Richard Genoud 2014-04-16 14:42 ` Vivek Gautam 2014-04-16 14:42 ` Vivek Gautam 2014-04-16 14:42 ` Vivek Gautam
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='CAFp+6iFFW8XQg_UtYEZfaiENULZDD8A7_9fr4f2no=qfau7-sQ@mail.gmail.com' \ --to=gautamvivek1987@gmail.com \ --cc=balbi@ti.com \ --cc=devicetree@vger.kernel.org \ --cc=gregkh@linuxfoundation.org \ --cc=jg1.han@samsung.com \ --cc=k.debski@samsung.com \ --cc=kgene.kim@samsung.com \ --cc=kishon@ti.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-doc@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-samsung-soc@vger.kernel.org \ --cc=linux-usb@vger.kernel.org \ --cc=sylvester.nawrocki@gmail.com \ --cc=t.figa@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: linkBe 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.