From: zhangfei <zhangfei.gao@linaro.org>
To: Ramiro Oliveira <Ramiro.Oliveira@synopsys.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Wolfram Sang <wsa@the-dreams.de>,
"mika.westerberg@linux.intel.com"
<mika.westerberg@linux.intel.com>,
"jarkko.nikula@linux.intel.com" <jarkko.nikula@linux.intel.com>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH v2] i2c: designware: add reset interface
Date: Fri, 16 Dec 2016 11:01:29 +0800 [thread overview]
Message-ID: <49a5d8a4-864e-e80e-eee0-57c876d25aaf@linaro.org> (raw)
In-Reply-To: <fd0afd5f-6ee4-a06f-2d03-444f71662c1b@linaro.org>
Hi, Philipp
On 2016年12月16日 10:45, zhangfei wrote:
>
>
> On 2016年12月15日 23:30, Ramiro Oliveira wrote:
>> Hi Andy and Zhangfei
>>
>> On 12/15/2016 12:33 PM, Andy Shevchenko wrote:
>>> On Thu, 2016-12-15 at 16:59 +0800, Zhangfei Gao wrote:
>>>> Some platforms like hi3660 need do reset first to allow accessing
>>>> registers
>>> Patch itself looks good, but would be nice to have it tested.
>>>
>>> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>>>
>> I tested the patch and it's working for the ARC architecture.
>>
>>>> Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>
>>>> ---
>>>> drivers/i2c/busses/i2c-designware-core.h | 1 +
>>>> drivers/i2c/busses/i2c-designware-platdrv.c | 28
>>>> ++++++++++++++++++++++++----
>>>> 2 files changed, 25 insertions(+), 4 deletions(-)
>>>>
>>>> diff --git a/drivers/i2c/busses/i2c-designware-core.h
>>>> b/drivers/i2c/busses/i2c-designware-core.h
>>>> index 0d44d2a..94b14fa 100644
>>>> --- a/drivers/i2c/busses/i2c-designware-core.h
>>>> +++ b/drivers/i2c/busses/i2c-designware-core.h
>>>> @@ -80,6 +80,7 @@ struct dw_i2c_dev {
>>>> void __iomem *base;
>>>> struct completion cmd_complete;
>>>> struct clk *clk;
>>>> + struct reset_control *rst;
>>>> u32 (*get_clk_rate_khz) (struct
>>>> dw_i2c_dev *dev);
>>>> struct dw_pci_controller *controller;
>>>> int cmd_err;
>>>> diff --git a/drivers/i2c/busses/i2c-designware-platdrv.c
>>>> b/drivers/i2c/busses/i2c-designware-platdrv.c
>>>> index 0b42a12..e9016ae 100644
>>>> --- a/drivers/i2c/busses/i2c-designware-platdrv.c
>>>> +++ b/drivers/i2c/busses/i2c-designware-platdrv.c
>>>> @@ -38,6 +38,7 @@
>>>> #include <linux/pm_runtime.h>
>>>> #include <linux/property.h>
>>>> #include <linux/io.h>
>>>> +#include <linux/reset.h>
>>>> #include <linux/slab.h>
>>>> #include <linux/acpi.h>
>>>> #include <linux/platform_data/i2c-designware.h>
>>>> @@ -176,6 +177,14 @@ static int dw_i2c_plat_probe(struct
>>>> platform_device *pdev)
>>>> dev->irq = irq;
>>>> platform_set_drvdata(pdev, dev);
>>>> + dev->rst = devm_reset_control_get_optional(&pdev->dev, NULL);
>> devm_reset_control_get_optional() is deprecated as explained in
>> linux/reset.h,
>> you should use devm_reset_control_get_optional_exclusive() or
>> devm_reset_control_get_optional_shared() instead, as applicable.
>>
>> I submitted a similar patch earlier today and I made the same mistake.
>
> Thanks Ramiro for the info
> Will use devm_reset_control_get_optional_exclusive instead.
> But should the interface be as simple as possible?
>
> Thanks
Sorry, a bit confused.
Is that mean we should not use devm_reset_control_get_optional()
While driver should decide whether use
devm_reset_control_get_optional_exclusive() or
devm_reset_control_get_optional_shared()
What if different platform has different requirement?
Looks the difference between _exclusive and _shared is refcount,
How about handle this inside, and not decided by interface?
Thanks
next prev parent reply other threads:[~2016-12-16 3:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 4:41 [PATCH] i2c: designware: add reset interface Zhangfei Gao
2016-12-13 20:34 ` Wolfram Sang
2016-12-14 19:00 ` Andy Shevchenko
2016-12-15 8:56 ` zhangfei
2016-12-15 8:59 ` [PATCH v2] " Zhangfei Gao
2016-12-15 12:33 ` Andy Shevchenko
2016-12-15 14:11 ` Phil Reid
2016-12-15 15:40 ` Jarkko Nikula
2016-12-15 15:30 ` Ramiro Oliveira
2016-12-16 2:45 ` zhangfei
2016-12-16 3:01 ` zhangfei [this message]
2016-12-23 10:26 ` Philipp Zabel
2016-12-23 13:39 ` zhangfei
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=49a5d8a4-864e-e80e-eee0-57c876d25aaf@linaro.org \
--to=zhangfei.gao@linaro.org \
--cc=Ramiro.Oliveira@synopsys.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=p.zabel@pengutronix.de \
--cc=wsa@the-dreams.de \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).