From: Sekhar Nori <nsekhar@ti.com>
To: "Manjunathappa, Prakash" <prakash.pm@ti.com>
Cc: linux-mmc@vger.kernel.org, mporter@ti.com,
davinci-linux-open-source@linux.davincidsp.com,
gregkh@linuxfoundation.org, cjb@laptop.org
Subject: Re: [PATCH] mmc: davinci: allow driver to work without DMA resource
Date: Fri, 1 Feb 2013 12:27:04 +0530 [thread overview]
Message-ID: <510B6740.7050808@ti.com> (raw)
In-Reply-To: <1359620433-3546-1-git-send-email-prakash.pm@ti.com>
On 1/31/2013 1:50 PM, Manjunathappa, Prakash wrote:
> Do not return probe failure with missing DMA resources,
> allow driver to work in PIO mode.
> Tested on da850-evm.
It will be nice to mention what exactly was tested. rootfs mount? file
create/deletion? mount/unmount?
> Signed-off-by: Manjunathappa, Prakash <prakash.pm@ti.com>
> ---
> drivers/mmc/host/davinci_mmc.c | 10 ++++++----
> 1 files changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/mmc/host/davinci_mmc.c b/drivers/mmc/host/davinci_mmc.c
> index 2063677..382b79d 100644
> --- a/drivers/mmc/host/davinci_mmc.c
> +++ b/drivers/mmc/host/davinci_mmc.c
> @@ -1190,13 +1190,15 @@ static int __init davinci_mmcsd_probe(struct platform_device *pdev)
>
> r = platform_get_resource(pdev, IORESOURCE_DMA, 0);
> if (!r)
> - goto out;
> - host->rxdma = r->start;
> + dev_warn(&pdev->dev, "DMA resource not specified\n");
Why not be specific and call it "RX DMA" instead. Anyone who gets this
error will have to do that anyway since you have now got two identical
error messages.
> + else
> + host->rxdma = r->start;
>
> r = platform_get_resource(pdev, IORESOURCE_DMA, 1);
> if (!r)
> - goto out;
> - host->txdma = r->start;
> + dev_warn(&pdev->dev, "DMA resource not specified\n");
"TX DMA" here.
Thanks,
Sekhar
next prev parent reply other threads:[~2013-02-01 6:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 8:20 [PATCH] mmc: davinci: allow driver to work without DMA resource Manjunathappa, Prakash
2013-02-01 6:57 ` Sekhar Nori [this message]
2013-02-04 13:27 ` Manjunathappa, Prakash
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=510B6740.7050808@ti.com \
--to=nsekhar@ti.com \
--cc=cjb@laptop.org \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mporter@ti.com \
--cc=prakash.pm@ti.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).