[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2fed95d6-72a0-328e-806c-ba214b52ff11@gmail.com>
Date: Sat, 7 Dec 2019 09:52:11 -0800
From: Florian Fainelli <f.fainelli@...il.com>
To: Ray Jui <ray.jui@...adcom.com>,
Florian Fainelli <f.fainelli@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>
Cc: devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
bcm-kernel-feedback-list@...adcom.com,
Rayagonda Kokatanur <rayagonda.kokatanur@...adcom.com>
Subject: Re: [PATCH 2/2] soc: bcm: iproc: Add Broadcom iProc IDM driver
On 12/6/2019 5:15 PM, Ray Jui wrote:
>>
>> Did not you intend to drop the reference count on elog_np here?
>>
>
> Sorry, I'm not following this comment. Could you please help to clarify
> for me a bit more? Thanks!
I meant that you drop the reference count on 'np' but you called
functions that incremented the reference count on 'elog_np', so maybe
you are not doing the of_node_put() on the appropriate device_node
reference?
>
>> [snip]
>>
>>> +static struct platform_driver iproc_idm_driver = {
>>> + .probe = iproc_idm_probe,
>>
>> Do not you need a remove function in order to unregister the sysfs file
>> that you created in iproc_idm_dev_probe() to avoid bind/unbind (or
>> rmmod/modprobe) to spit out an existing sysfs entry warning?
>>
>
> This driver should never be compiled as a module. It's meant to be
> always there to capture IDM bus timeouts.
>
> But you are right that I cannot prevent user from trying to unbind it
> for whatever reason. I'll add a remove routine to take care of this.
You can also set suppress_bind_attrs to your platform_driver structure
to prevent unbind/bind from happening.
--
Florian
Powered by blists - more mailing lists