RE: [PATCH RFC] mfd: syscon: Decouple syscon interface from syscon devices
Hi Arnd, On Wednesday, June 18, 2014 Arnd wrote: > To: Tomasz Figa > Cc: linux-arm-ker...@lists.infradead.org; mark.br...@linaro.org; Tomasz Figa; > linux-samsung-soc@vger.kernel.org; Kukjin Kim; Russell King - ARM Linux; Samuel > Ortiz; Pankaj Dubey; linux-ker...@vger.kernel.org; jo...@samsung.com; > vikas.saj...@samsung.com; chow@samsung.com; Lee Jones > Subject: Re: [PATCH RFC] mfd: syscon: Decouple syscon interface from syscon > devices > > On Tuesday 17 June 2014 23:26:22 Tomasz Figa wrote: > > On 17.06.2014 17:42, Arnd Bergmann wrote: > > > This seems like a reasonable way of solving the problem, but I think > > > there is an even better one that we have about in the past: if we > > > promote syscon from a platform driver into a a drivers/base/ helper > > > that is independent of the platform device matching, we can use call > > > syscon_regmap_lookup_* for any device node, whether it's already > > > bound to a driver or not, which do what you need. It would also make > > > it easier to call the syscon code before the platform_device > > > infrastructure gets initialized, which is something a number of > > > people have asked for, e.g. for using regmap to do SMP bringup or > > > for clock registration. > > > > Basically, unless I'm missing your point, this is what my patch does, > > except that I don't move it to drivers/base/ and the registration > > function I added require a pointer to struct device. Indeed, > > decoupling it further from the driver model, by adding > > of_syscon_register() should be useful for early users. > > I believe the part you are missing is that with the approach I suggested, there would > be no registration function at all. You can easily do the lookup from the client drivers > using the DT data structures, with no need for the device at all. Will you please elaborate more on this? The only exception > today is the clps711x platform using syscon_regmap_lookup_by_pdevname(), but > that should be solved in 3.17 when clps711x becomes DT-only. > Does it mean that this may become a blocking issue for this patch to go before 3.17? If yes, isn't it will be good to accept this patch as it is if it's not causing issue or breaking anything with existing users of syscon. At least for our use of converting Exynos PMU and PM related consolidation this change is working fine and we have verified it. > > Should I move this to drivers/base/, even though from current location > > it can be used outside the platform driver anyway? > > Thinking about it some more, drivers/of might be better than drivers/base. > It depends a bit where we are heading with this, in particular if we expect to see non- > DT users in the future. > > Arnd Thanks, Pankaj Dubey -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH RFC] mfd: syscon: Decouple syscon interface from syscon devices
Hi, On Wednesday, June 18 2014, Lee Jones wrote: > On Tue, 17 Jun 2014, Tomasz Figa wrote: > > On 17.06.2014 17:42, Arnd Bergmann wrote: > > > On Tuesday 17 June 2014 17:32:44 Tomasz Figa wrote: > > >> Currently a syscon entity can be only registered directly through a > > >> platform device that binds to a dedicated driver. However in > > >> certain use cases it is desirable to make a device used with > > >> another driver a syscon interface provider. For example, certain > > >> SoCs (e.g. Exynos) contain system controller blocks which perform > > >> various functions such as power domain control, CPU power > > >> management, low power mode control, but in addition contain certain > > >> IP integration glue, such as various signal masks, coprocessor > > >> power control, etc. In such case, there is a need to have a > > >> dedicated driver for such system controller but also share > > >> registers with other drivers. The latter is where the syscon interface > > >> is helpful. > > >> > > >> This patch decouples syscon object from syscon driver, so that it > > >> can be registered from any driver in addition to the original > > >> "syscon" platform driver. > > +1 for this approach. > > Michal, Pankay, > Does it also suit your needs? > Sorry for late reply. I tested this patch after changing exynos PMU to be a syscon provider and it's working well. So if we can address Arnd's comments, this patch will be helpful in making exynos PMU a complete platform driver. Thanks, Pankaj Dubey > > >> Signed-off-by: Tomasz Figa > > > > > > Hi Tomasz, > > > > > > This seems like a reasonable way of solving the problem, but I think > > > there is an even better one that we have about in the past: if we > > > promote syscon from a platform driver into a a drivers/base/ helper > > > that is independent of the platform device matching, we can use call > > > syscon_regmap_lookup_* for any device node, whether it's already > > > bound to a driver or not, which do what you need. It would also make > > > it easier to call the syscon code before the platform_device > > > infrastructure gets initialized, which is something a number of > > > people have asked for, e.g. for using regmap to do SMP bringup or > > > for clock registration. > > > > Basically, unless I'm missing your point, this is what my patch does, > > except that I don't move it to drivers/base/ and the registration > > function I added require a pointer to struct device. Indeed, > > decoupling it further from the driver model, by adding > > of_syscon_register() should be useful for early users. > > If agreed by Arnd, I think this work can be completed as a subsequent patch. > > > Should I move this to drivers/base/, even though from current location > > it can be used outside the platform driver anyway? > > If I'm being honest with myself, I'd say that Syscon wasn't really an MFD > driver. I'm > happy to keep it in there any continue maintaining it, but wouldn't block a > move > either. > > -- > Lee Jones > Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software > for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH RFC] mfd: syscon: Decouple syscon interface from syscon devices
Hi, On 06/18/2014 02:57 PM, Arnd Bergmann wrote: > On Tuesday 17 June 2014 23:26:22 Tomasz Figa wrote: >> On 17.06.2014 17:42, Arnd Bergmann wrote: >>> This seems like a reasonable way of solving the problem, but I think >>> there is an even better one that we have about in the past: if we >>> promote syscon from a platform driver into a a drivers/base/ helper >>> that is independent of the platform device matching, we can use >>> call syscon_regmap_lookup_* for any device node, whether it's already >>> bound to a driver or not, which do what you need. It would also make >>> it easier to call the syscon code before the platform_device >>> infrastructure gets initialized, which is something a number of >>> people have asked for, e.g. for using regmap to do SMP bringup >>> or for clock registration. >> >> Basically, unless I'm missing your point, this is what my patch does, >> except that I don't move it to drivers/base/ and the registration >> function I added require a pointer to struct device. Indeed, decoupling >> it further from the driver model, by adding of_syscon_register() should >> be useful for early users. > > I believe the part you are missing is that with the approach I suggested, > there would be no registration function at all. You can easily do the > lookup from the client drivers using the DT data structures, with no > need for the device at all. The only exception today is the clps711x > platform using syscon_regmap_lookup_by_pdevname(), but that should be > solved in 3.17 when clps711x becomes DT-only. I agree with Arnd. This patch is doing the part of what we wanted to do with it. It means create a list of registered devices. But you are working with struct device which you can't use in early phase which is the feature we wanted to use. But currently we have workaround in the kernel and clk subsystem is not able to work with regmap anyway. Moving to proper location is just the last step. Thanks, Michal -- Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91 w: www.monstr.eu p: +42-0-721842854 Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/ Maintainer of Linux kernel - Xilinx Zynq ARM architecture Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform signature.asc Description: OpenPGP digital signature
Re: [PATCH RFC] mfd: syscon: Decouple syscon interface from syscon devices
On Tuesday 17 June 2014 23:26:22 Tomasz Figa wrote: > On 17.06.2014 17:42, Arnd Bergmann wrote: > > This seems like a reasonable way of solving the problem, but I think > > there is an even better one that we have about in the past: if we > > promote syscon from a platform driver into a a drivers/base/ helper > > that is independent of the platform device matching, we can use > > call syscon_regmap_lookup_* for any device node, whether it's already > > bound to a driver or not, which do what you need. It would also make > > it easier to call the syscon code before the platform_device > > infrastructure gets initialized, which is something a number of > > people have asked for, e.g. for using regmap to do SMP bringup > > or for clock registration. > > Basically, unless I'm missing your point, this is what my patch does, > except that I don't move it to drivers/base/ and the registration > function I added require a pointer to struct device. Indeed, decoupling > it further from the driver model, by adding of_syscon_register() should > be useful for early users. I believe the part you are missing is that with the approach I suggested, there would be no registration function at all. You can easily do the lookup from the client drivers using the DT data structures, with no need for the device at all. The only exception today is the clps711x platform using syscon_regmap_lookup_by_pdevname(), but that should be solved in 3.17 when clps711x becomes DT-only. > Should I move this to drivers/base/, even though from current location > it can be used outside the platform driver anyway? Thinking about it some more, drivers/of might be better than drivers/base. It depends a bit where we are heading with this, in particular if we expect to see non-DT users in the future. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH RFC] mfd: syscon: Decouple syscon interface from syscon devices
On Tue, 17 Jun 2014, Tomasz Figa wrote: > On 17.06.2014 17:42, Arnd Bergmann wrote: > > On Tuesday 17 June 2014 17:32:44 Tomasz Figa wrote: > >> Currently a syscon entity can be only registered directly through a > >> platform device that binds to a dedicated driver. However in certain use > >> cases it is desirable to make a device used with another driver a syscon > >> interface provider. For example, certain SoCs (e.g. Exynos) contain > >> system controller blocks which perform various functions such as power > >> domain control, CPU power management, low power mode control, but in > >> addition contain certain IP integration glue, such as various signal > >> masks, coprocessor power control, etc. In such case, there is a need to > >> have a dedicated driver for such system controller but also share > >> registers with other drivers. The latter is where the syscon interface > >> is helpful. > >> > >> This patch decouples syscon object from syscon driver, so that it can be > >> registered from any driver in addition to the original "syscon" platform > >> driver. +1 for this approach. Michal, Pankay, Does it also suit your needs? > >> Signed-off-by: Tomasz Figa > > > > Hi Tomasz, > > > > This seems like a reasonable way of solving the problem, but I think > > there is an even better one that we have about in the past: if we > > promote syscon from a platform driver into a a drivers/base/ helper > > that is independent of the platform device matching, we can use > > call syscon_regmap_lookup_* for any device node, whether it's already > > bound to a driver or not, which do what you need. It would also make > > it easier to call the syscon code before the platform_device > > infrastructure gets initialized, which is something a number of > > people have asked for, e.g. for using regmap to do SMP bringup > > or for clock registration. > > Basically, unless I'm missing your point, this is what my patch does, > except that I don't move it to drivers/base/ and the registration > function I added require a pointer to struct device. Indeed, decoupling > it further from the driver model, by adding of_syscon_register() should > be useful for early users. If agreed by Arnd, I think this work can be completed as a subsequent patch. > Should I move this to drivers/base/, even though from current location > it can be used outside the platform driver anyway? If I'm being honest with myself, I'd say that Syscon wasn't really an MFD driver. I'm happy to keep it in there any continue maintaining it, but wouldn't block a move either. -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH RFC] mfd: syscon: Decouple syscon interface from syscon devices
Hi Arnd, On 17.06.2014 17:42, Arnd Bergmann wrote: > On Tuesday 17 June 2014 17:32:44 Tomasz Figa wrote: >> Currently a syscon entity can be only registered directly through a >> platform device that binds to a dedicated driver. However in certain use >> cases it is desirable to make a device used with another driver a syscon >> interface provider. For example, certain SoCs (e.g. Exynos) contain >> system controller blocks which perform various functions such as power >> domain control, CPU power management, low power mode control, but in >> addition contain certain IP integration glue, such as various signal >> masks, coprocessor power control, etc. In such case, there is a need to >> have a dedicated driver for such system controller but also share >> registers with other drivers. The latter is where the syscon interface >> is helpful. >> >> This patch decouples syscon object from syscon driver, so that it can be >> registered from any driver in addition to the original "syscon" platform >> driver. >> >> Signed-off-by: Tomasz Figa > > Hi Tomasz, > > This seems like a reasonable way of solving the problem, but I think > there is an even better one that we have about in the past: if we > promote syscon from a platform driver into a a drivers/base/ helper > that is independent of the platform device matching, we can use > call syscon_regmap_lookup_* for any device node, whether it's already > bound to a driver or not, which do what you need. It would also make > it easier to call the syscon code before the platform_device > infrastructure gets initialized, which is something a number of > people have asked for, e.g. for using regmap to do SMP bringup > or for clock registration. Basically, unless I'm missing your point, this is what my patch does, except that I don't move it to drivers/base/ and the registration function I added require a pointer to struct device. Indeed, decoupling it further from the driver model, by adding of_syscon_register() should be useful for early users. Should I move this to drivers/base/, even though from current location it can be used outside the platform driver anyway? Best regards, Tomasz -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH RFC] mfd: syscon: Decouple syscon interface from syscon devices
On Tuesday 17 June 2014 17:32:44 Tomasz Figa wrote: > Currently a syscon entity can be only registered directly through a > platform device that binds to a dedicated driver. However in certain use > cases it is desirable to make a device used with another driver a syscon > interface provider. For example, certain SoCs (e.g. Exynos) contain > system controller blocks which perform various functions such as power > domain control, CPU power management, low power mode control, but in > addition contain certain IP integration glue, such as various signal > masks, coprocessor power control, etc. In such case, there is a need to > have a dedicated driver for such system controller but also share > registers with other drivers. The latter is where the syscon interface > is helpful. > > This patch decouples syscon object from syscon driver, so that it can be > registered from any driver in addition to the original "syscon" platform > driver. > > Signed-off-by: Tomasz Figa Hi Tomasz, This seems like a reasonable way of solving the problem, but I think there is an even better one that we have about in the past: if we promote syscon from a platform driver into a a drivers/base/ helper that is independent of the platform device matching, we can use call syscon_regmap_lookup_* for any device node, whether it's already bound to a driver or not, which do what you need. It would also make it easier to call the syscon code before the platform_device infrastructure gets initialized, which is something a number of people have asked for, e.g. for using regmap to do SMP bringup or for clock registration. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
