On Thu, Nov 21, 2024 at 03:11:30PM +0100, Thomas Weißschuh wrote: > On 2024-11-21 15:00:13+0100, Krzysztof Kozlowski wrote: > > On 21/11/2024 14:47, Thomas Weißschuh wrote: > > > > > >> + > > >> + return 0; > > >> +} > > >> + > > >> +static const struct platform_device_id cros_ec_charge_state_id[] = { > > >> + { DRV_NAME, 0 }, > > >> + {} > > >> +}; > > > > > > Reference this in the platform_driver below. > > > > And missing module device table... This wasn't ever tested as module. > > It has one in the general MODULE_*() macro soup at the end of the file. > But yes, it should be moved where it can be found, right after > cros_ec_charge_state_id. Thank you all for spending time reviewing my changes, and I am very sorry that I made so such careless mistakes. All these input are very valuable, and I learnt a lot from them, and I will prevent these mistakes in future commits. As we have seen lots of inputs from the DTS change commit, and I spent lot of time coming up a better solution for achieving my goal (export certain mechanisms, such that we can limit the charger chip current as a cooling device), I think maybe extending functionalities in the driver/power/supply/cros_usbpd-charger.c would be a better approach. As a result, I will stop the development on this series. So anyone is helping on this series can stop review these changes. However, because I am kind of new to developing the kernel driver module, any inputs are welcome, and I have to say I really learnt a lot from mistakes pointed by all of you, and I shall not make same mistakes in future contributions. Best, Sung-Chi Li