linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kheitke@codeaurora.org (Kenneth Heitke)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] i2c: QUP based bus driver for Qualcomm MSM chipsets
Date: Thu, 09 Sep 2010 14:52:19 -0600	[thread overview]
Message-ID: <4C894903.1050909@codeaurora.org> (raw)
In-Reply-To: <AANLkTimHQ=ag5z+SKbGrm5BD-eF+xcDuKp4R_=4tf3cP@mail.gmail.com>

Sundar wrote:
> Hi Kenneth,
> 
> just some error codes and leaks if I am right :)
> 
> On Wed, Sep 8, 2010 at 6:29 AM, Kenneth Heitke <kheitke@codeaurora.org> wrote:
>> +
>> +static int __devinit
>> +qup_i2c_probe(struct platform_device *pdev)
>> +{
>> +
>> +       qup_mem = platform_get_resource_byname(pdev, IORESOURCE_MEM,
>> +                                               "qup_phys_addr");
>> +       if (!qup_mem) {
>> +               dev_err(&pdev->dev, "no qup mem resource?\n");
>> +               return -ENODEV;
> 
> I think this should be -ENXIO instead of -ENODEV?
> 
>> +       gsbi_mem = platform_get_resource_byname(pdev, IORESOURCE_MEM,
>> +                                               "gsbi_qup_i2c_addr");
>> +       if (!gsbi_mem) {
>> +               dev_err(&pdev->dev, "no gsbi mem resource?\n");
>> +               return -ENODEV;
> 
> Ditto here.
> 
>> +       in_irq = platform_get_resource_byname(pdev, IORESOURCE_IRQ,
>> +                                               "qup_in_intr");
>> +
>> +       out_irq = platform_get_resource_byname(pdev, IORESOURCE_IRQ,
>> +                                               "qup_out_intr");
>> +
>> +       err_irq = platform_get_resource_byname(pdev, IORESOURCE_IRQ,
>> +                                               "qup_err_intr");
>> +       if (!err_irq) {
>> +               dev_err(&pdev->dev, "no error irq resource?\n");
>> +               return -ENODEV;
>> +       }
> 
> All the same here too?
> 
>> +
>> +       qup_io = devm_request_mem_region(&pdev->dev, qup_mem->start,
>> +                       resource_size(qup_mem), pdev->name);
>> +       if (!qup_io) {
>> +               dev_err(&pdev->dev, "QUP region already claimed\n");
>> +               return -EBUSY;
>> +       }
>> +
>> +       gsbi_io = devm_request_mem_region(&pdev->dev, gsbi_mem->start,
>> +                       resource_size(gsbi_mem), pdev->name);
>> +       if (!gsbi_io) {
>> +               dev_err(&pdev->dev, "GSBI region already claimed\n");
>> +               return -EBUSY;
>> +       }
>> +
>> +       dev = devm_kzalloc(&pdev->dev, sizeof(struct qup_i2c_dev), GFP_KERNEL);
> 
> [..]
> 
>> +       if (!dev->base)
>> +               return -ENOMEM;
> 
> Missing *_kzfree whilst returning?
> 
>> +       dev->gsbi = devm_ioremap(&pdev->dev,
>> +                       gsbi_mem->start, resource_size(gsbi_mem));
>> +       if (!dev->gsbi)
>> +               return -ENOMEM;
>> +
>> +       clk = clk_get(&pdev->dev, "qup_clk");
>> +       if (IS_ERR(clk)) {
>> +               dev_err(&pdev->dev, "Could not get clock\n");
>> +               ret = PTR_ERR(clk);
>> +               goto err_clk_get_failed;
> 
> Will not the devm_iounmap be needed here?
> 
> Thanx!
> Sundar
> 

Hopefully no leaks since I am using the devm_ calls.  The resources 
should be freed up automatically on device release and if the probe 
function fails.  Please let me know if this assumption is not correct.

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  reply	other threads:[~2010-09-09 20:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08  0:59 [PATCH v3] i2c: QUP based bus driver for Qualcomm MSM chipsets Kenneth Heitke
2010-09-08 13:23 ` Trilok Soni
2010-09-09 19:01 ` Sundar
2010-09-09 20:52   ` Kenneth Heitke [this message]
2010-09-26 23:04   ` Ben Dooks

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=4C894903.1050909@codeaurora.org \
    --to=kheitke@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).