From: Kishon Vijay Abraham I <kishon@ti.com> To: Tony Lindgren <tony@atomide.com> Cc: Arnd Bergmann <arnd@arndb.de>, <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>, <robh+dt@kernel.org>, <pawel.moll@arm.com>, <mark.rutland@arm.com>, <ijc+devicetree@hellion.org.uk>, <galak@codeaurora.org>, <rogerq@ti.com>, <nsekhar@ti.com>, <linux-pci@vger.kernel.org>, <linux-usb@vger.kernel.org>, <t-kristo@ti.com> Subject: Re: [PATCH v3 0/9] phy: use syscon framework APIs to set ctrl mod reg Date: Fri, 18 Dec 2015 15:46:21 +0530 [thread overview] Message-ID: <5673DCF5.1050603@ti.com> (raw) In-Reply-To: <20151215152659.GQ23396@atomide.com> Hi, On Tuesday 15 December 2015 08:56 PM, Tony Lindgren wrote: > * Kishon Vijay Abraham I <kishon@ti.com> [151215 04:47]: >> On Tuesday 15 December 2015 05:25 PM, Arnd Bergmann wrote: >>>>> >>>>> Can you explain here what the conversion is good for? Why do you >>>>> prefer the syscon mapping over a high-level driver in this case? >>>> >>>> phy-omap-control driver was added when there was no proper >>>> infrastructure for doing control module initializations. The >>>> phy-omap-control driver is not an 'actual' PHY driver and it >>>> was just a hack to do PHY related control module initializations. >>>> phy-omap-control is also getting unmanageable with the number of >>>> platforms each having number of modules (like USB, SATA, PCIe), >>>> using the same driver for control module initializations. >>>> >>>> Now with SYSCON framework being added to the kernel, phy-omap-control >>>> shouldn't be needed and it also provides a uniform API across all the >>>> modules to program the control module. >>> >>> Ok, so the "phy-control" devices were really just a few registers of >>> a system controller device that does a lot of other things as well, right? >> >> right. >>> >>> Can you put your description above into the cover-letter for the series, >>> and the merge commit? > > Just to confirm.. Seems like this series keeps USB working and the dts > changes can be done later after the driver changes have been merged? that's right Tony. Will merge this series by tomorrow if I don't get any review comments. Thanks Kishon > > Regards, > > Tony > -- > To unsubscribe from this list: send the line "unsubscribe linux-pci" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >
WARNING: multiple messages have this Message-ID (diff)
From: Kishon Vijay Abraham I <kishon@ti.com> To: Tony Lindgren <tony@atomide.com> Cc: Arnd Bergmann <arnd@arndb.de>, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com, ijc+devicetree@hellion.org.uk, galak@codeaurora.org, rogerq@ti.com, nsekhar@ti.com, linux-pci@vger.kernel.org, linux-usb@vger.kernel.org, t-kristo@ti.com Subject: Re: [PATCH v3 0/9] phy: use syscon framework APIs to set ctrl mod reg Date: Fri, 18 Dec 2015 15:46:21 +0530 [thread overview] Message-ID: <5673DCF5.1050603@ti.com> (raw) In-Reply-To: <20151215152659.GQ23396@atomide.com> Hi, On Tuesday 15 December 2015 08:56 PM, Tony Lindgren wrote: > * Kishon Vijay Abraham I <kishon@ti.com> [151215 04:47]: >> On Tuesday 15 December 2015 05:25 PM, Arnd Bergmann wrote: >>>>> >>>>> Can you explain here what the conversion is good for? Why do you >>>>> prefer the syscon mapping over a high-level driver in this case? >>>> >>>> phy-omap-control driver was added when there was no proper >>>> infrastructure for doing control module initializations. The >>>> phy-omap-control driver is not an 'actual' PHY driver and it >>>> was just a hack to do PHY related control module initializations. >>>> phy-omap-control is also getting unmanageable with the number of >>>> platforms each having number of modules (like USB, SATA, PCIe), >>>> using the same driver for control module initializations. >>>> >>>> Now with SYSCON framework being added to the kernel, phy-omap-control >>>> shouldn't be needed and it also provides a uniform API across all the >>>> modules to program the control module. >>> >>> Ok, so the "phy-control" devices were really just a few registers of >>> a system controller device that does a lot of other things as well, right? >> >> right. >>> >>> Can you put your description above into the cover-letter for the series, >>> and the merge commit? > > Just to confirm.. Seems like this series keeps USB working and the dts > changes can be done later after the driver changes have been merged? that's right Tony. Will merge this series by tomorrow if I don't get any review comments. Thanks Kishon > > Regards, > > Tony > -- > To unsubscribe from this list: send the line "unsubscribe linux-pci" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >
next prev parent reply other threads:[~2015-12-18 10:16 UTC|newest] Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-12-15 9:15 [PATCH v3 0/9] phy: use syscon framework APIs to set ctrl mod reg Kishon Vijay Abraham I 2015-12-15 9:15 ` Kishon Vijay Abraham I 2015-12-15 9:16 ` [PATCH v3 1/9] phy: ti-pipe3: introduce local struct device* in probe Kishon Vijay Abraham I 2015-12-15 9:16 ` Kishon Vijay Abraham I 2015-12-15 9:16 ` [PATCH v3 2/9] phy: ti-pipe3: move clk initialization to a separate function Kishon Vijay Abraham I 2015-12-15 9:16 ` Kishon Vijay Abraham I 2015-12-15 9:16 ` [PATCH v3 3/9] phy: ti-pipe3: move sysctrl " Kishon Vijay Abraham I 2015-12-15 9:16 ` Kishon Vijay Abraham I 2015-12-15 9:16 ` [PATCH v3 4/9] phy: ti-pipe3: move mem resource " Kishon Vijay Abraham I 2015-12-15 9:16 ` Kishon Vijay Abraham I 2015-12-15 9:16 ` [PATCH v3 5/9] phy: ti-pipe3: use ti_pipe3_power_off to power off the PHY during probe Kishon Vijay Abraham I 2015-12-15 9:16 ` Kishon Vijay Abraham I 2015-12-15 9:16 ` [PATCH v3 6/9] phy: ti-pipe3: use *syscon* framework API to power on/off the PHY Kishon Vijay Abraham I 2015-12-15 9:16 ` Kishon Vijay Abraham I 2015-12-20 3:38 ` Rob Herring 2015-12-21 8:36 ` Kishon Vijay Abraham I 2015-12-21 8:36 ` Kishon Vijay Abraham I 2015-12-15 9:16 ` [PATCH v3 7/9] phy: ti-pipe3: use *syscon* framework API to set PCS value of " Kishon Vijay Abraham I 2015-12-15 9:16 ` Kishon Vijay Abraham I 2015-12-20 3:38 ` Rob Herring 2015-12-15 9:16 ` [PATCH v3 8/9] phy: omap-usb2: use omap_usb_power_off to power off the PHY during probe Kishon Vijay Abraham I 2015-12-15 9:16 ` Kishon Vijay Abraham I 2015-12-15 9:16 ` [PATCH v3 9/9] phy: omap-usb2: use *syscon* framework API to power on/off the PHY Kishon Vijay Abraham I 2015-12-15 9:16 ` Kishon Vijay Abraham I 2015-12-20 3:39 ` Rob Herring 2015-12-20 12:07 ` Kishon Vijay Abraham I 2015-12-20 12:07 ` Kishon Vijay Abraham I 2015-12-22 18:19 ` Rob Herring 2015-12-22 18:19 ` Rob Herring 2015-12-15 10:56 ` [PATCH v3 0/9] phy: use syscon framework APIs to set ctrl mod reg Arnd Bergmann 2015-12-15 11:14 ` Kishon Vijay Abraham I 2015-12-15 11:14 ` Kishon Vijay Abraham I 2015-12-15 11:55 ` Arnd Bergmann 2015-12-15 12:46 ` Kishon Vijay Abraham I 2015-12-15 12:46 ` Kishon Vijay Abraham I 2015-12-15 15:26 ` Tony Lindgren 2015-12-15 15:26 ` Tony Lindgren 2015-12-18 10:16 ` Kishon Vijay Abraham I [this message] 2015-12-18 10:16 ` Kishon Vijay Abraham I
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=5673DCF5.1050603@ti.com \ --to=kishon@ti.com \ --cc=arnd@arndb.de \ --cc=devicetree@vger.kernel.org \ --cc=galak@codeaurora.org \ --cc=ijc+devicetree@hellion.org.uk \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=linux-pci@vger.kernel.org \ --cc=linux-usb@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=nsekhar@ti.com \ --cc=pawel.moll@arm.com \ --cc=robh+dt@kernel.org \ --cc=rogerq@ti.com \ --cc=t-kristo@ti.com \ --cc=tony@atomide.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.