ARM: OMAP2: Use custom soc attribute group instead of device_create_file
authorSudeep Holla <sudeep.holla@arm.com>
Sat, 23 May 2020 17:08:59 +0000 (18:08 +0100)
committerSudeep Holla <sudeep.holla@arm.com>
Mon, 6 Jul 2020 08:48:06 +0000 (09:48 +0100)
commit475d04b48b9e227e1be2396b1499bd36274be40a
tree8b61ae755a90eeae0df3de90c1b849cab2f0a385
parent53d421d29c052baa2c3f8d861781adc5cbcebe57
ARM: OMAP2: Use custom soc attribute group instead of device_create_file

Commit c31e73121f4c ("base: soc: Handle custom soc information sysfs
entries") introduced custom soc attribute group in soc_device_attribute
structure but there are no users treewide. While trying to understand
the motivation and tried to use it, it was found lot of existing custom
attributes can moved to use it instead of device_create_file.

Though most of these never remove/cleanup the custom attribute as they
never call soc_device_unregister, using these custom attribute group
eliminate the need for any cleanup as the driver infrastructure will
take care of that.

Let us remove device_create_file and start using the custom attribute
group in soc_device_attribute.

Link: https://lore.kernel.org/r/20200523170859.50003-9-sudeep.holla@arm.com
Cc: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Acked-by: Tony Lindgren <tony@atomide.com>
Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
arch/arm/mach-omap2/id.c