linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Wolfram Sang <wsa@the-dreams.de>, Michal Simek <michal.simek@xilinx.com>
Cc: Dejin Zheng <zhengdejin5@gmail.com>,
	harinik@xilinx.com, soren.brinkmann@xilinx.com,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] i2c: cadence: Add an error handling for platform_get_irq()
Date: Fri, 22 May 2020 17:26:40 +0200	[thread overview]
Message-ID: <7763d79e-3a44-2dbe-a4d3-45d40a3a1e02@xilinx.com> (raw)
In-Reply-To: <20200522151459.GK5670@ninjato>

On 22. 05. 20 17:14, Wolfram Sang wrote:
> 
>> The change is valid but the question is if make sense to do it in this
>> way. Some drivers are using devm_request_irq to do do job.
>>
>> For example:
>>  	id->irq = platform_get_irq(pdev, 0);
>>         ret = devm_request_irq(&pdev->dev, id->irq, cdns_i2c_isr, 0,
>>                                   DRIVER_NAME, id);
>>         if (ret)
>> 		return ret;
> 
> I like this version better. Maybe we should simply move the
> platform_get_irq() line to the devm_request_irq() call?

You know about
devm_platform_get_and_ioremap_resource()
usage.
 Maybe that's the way to go. Because as of today there is no way to pass
position of irq resource.

But I expect it will come in near future.

Thanks,
Michal


  reply	other threads:[~2020-05-22 15:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20 14:48 [PATCH v2] i2c: cadence: Add an error handling for platform_get_irq() Dejin Zheng
2020-05-22 11:24 ` Michal Simek
2020-05-22 15:14   ` Wolfram Sang
2020-05-22 15:26     ` Michal Simek [this message]
2020-05-22 20:19       ` Wolfram Sang
2020-05-23 13:36         ` Dejin Zheng
2020-05-23 15:26   ` Dejin Zheng

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=7763d79e-3a44-2dbe-a4d3-45d40a3a1e02@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=harinik@xilinx.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=soren.brinkmann@xilinx.com \
    --cc=wsa@the-dreams.de \
    --cc=zhengdejin5@gmail.com \
    /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).