From: Ladislav Michl <ladis@linux-mips.org>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: linux-usb@vger.kernel.org,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>
Subject: [1/2] usb: gadget: udc: atmel: Use devm_ioremap_resource()
Date: Mon, 22 Jan 2018 16:57:52 +0100 [thread overview]
Message-ID: <20180122155752.GA18617@lenoch> (raw)
On Mon, Jan 22, 2018 at 06:53:38PM +0300, Sergei Shtylyov wrote:
> On 01/22/2018 06:44 PM, Ladislav Michl wrote:
>
> >>> As devm_ioremap_resource() checks for valid resource,
> >>> make use of it instead of testing ourselves. As a bonus
> >>> memory region is requested.
> >>>
> >>> Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
> >>> ---
> >>> drivers/usb/gadget/udc/atmel_usba_udc.c | 40 ++++++++++++++++-----------------
> >>> 1 file changed, 19 insertions(+), 21 deletions(-)
> >>>
> >>> diff --git a/drivers/usb/gadget/udc/atmel_usba_udc.c b/drivers/usb/gadget/udc/atmel_usba_udc.c
> >>> index 075eaaa8a408..403e06e7175f 100644
> >>> --- a/drivers/usb/gadget/udc/atmel_usba_udc.c
> >>> +++ b/drivers/usb/gadget/udc/atmel_usba_udc.c
> >> [...]
> >>> @@ -2284,10 +2284,24 @@ static int usba_udc_probe(struct platform_device *pdev)
> >>> udc->gadget = usba_gadget_template;
> >>> INIT_LIST_HEAD(&udc->gadget.ep_list);
> >>>
> >>> - regs = platform_get_resource(pdev, IORESOURCE_MEM, CTRL_IOMEM_ID);
> >>> - fifo = platform_get_resource(pdev, IORESOURCE_MEM, FIFO_IOMEM_ID);
> >>> - if (!regs || !fifo)
> >>> - return -ENXIO;
> >>> + res = platform_get_resource(pdev, IORESOURCE_MEM, CTRL_IOMEM_ID);
> >>> + udc->regs = devm_ioremap_resource(&pdev->dev, res);
> >>> + if (IS_ERR(udc->regs)) {
> >>> + ret = PTR_ERR(udc->regs);
> >>> + dev_err(&pdev->dev, "Unable to map I/O memory: %d\n", ret);
> >>
> >> devm_ioremap_resource() prints out the error message.
> >
> > It does, indeed. However I left both error messages here to distinguish
> > between I/O and FIFO failures.
>
> Well, I'm seeing the successfully remapped resource being dumped below, so you can judge the probing progress by that message (and the resource dump done by devm_ioremap_resource())... but if you feel that not enough, OK, leave it as is...
I feel convinced and v2 will follow :-)
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-01-22 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 15:57 Ladislav Michl [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-22 15:53 [1/2] usb: gadget: udc: atmel: Use devm_ioremap_resource() Sergei Shtylyov
2018-01-22 15:44 Ladislav Michl
2018-01-22 15:34 Sergei Shtylyov
2018-01-22 15:21 Ladislav Michl
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=20180122155752.GA18617@lenoch \
--to=ladis@linux-mips.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=linux-usb@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=sergei.shtylyov@cogentembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.