From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: grant.likely@secretlab.ca, rob.herring@calxeda.com,
rob@landley.net, balbi@ti.com, gregkh@linuxfoundation.org,
devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [PATCH v2 6/7] usb: dwc3-omap: Minor fixes to get dt working
Date: Mon, 01 Oct 2012 20:00:41 +0200 [thread overview]
Message-ID: <5069DA49.7030901@mvista.com> (raw)
In-Reply-To: <1349087107-18229-7-git-send-email-kishon@ti.com>
Hello.
On 01-10-2012 12:25, Kishon Vijay Abraham I wrote:
> Includes few minor fixes in dwc3-omap like populating the compatible
> string in a correct way, extracting the utmi-mode property properly and
> changing the index of get_irq since irq of core is removed from hwmod
> entry.
> Also updated the documentation with dwc3-omap device tree binding
> information.
>
> Signed-off-by: Kishon Vijay Abraham I<kishon@ti.com>
> ---
> drivers/usb/dwc3/dwc3-omap.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/usb/dwc3/dwc3-omap.c b/drivers/usb/dwc3/dwc3-omap.c
> index c19affa..25bd847 100644
> --- a/drivers/usb/dwc3/dwc3-omap.c
> +++ b/drivers/usb/dwc3/dwc3-omap.c
> @@ -277,13 +277,13 @@ static int __devinit dwc3_omap_probe(struct platform_device *pdev)
>
> platform_set_drvdata(pdev, omap);
>
> - irq = platform_get_irq(pdev, 1);
> + irq = platform_get_irq(pdev, 0);
> if (irq< 0) {
> dev_err(dev, "missing IRQ resource\n");
> return -EINVAL;
> }
>
> - res = platform_get_resource(pdev, IORESOURCE_MEM, 1);
> + res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> if (!res) {
> dev_err(dev, "missing memory base resource\n");
> return -EINVAL;
> @@ -326,7 +326,7 @@ static int __devinit dwc3_omap_probe(struct platform_device *pdev)
>
> utmi_mode = of_get_property(node, "utmi-mode",&size);
> if (utmi_mode&& size == sizeof(*utmi_mode)) {
> - reg |= *utmi_mode;
> + reg |= be32_to_cpup(utmi_mode);
Why not just use of_property_read_u32() instead of all this?
WBR, Sergei
next prev parent reply other threads:[~2012-10-01 18:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 10:25 [PATCH v2 0/7] usb: dwc3-omap: add dt support Kishon Vijay Abraham I
2012-10-01 10:25 ` [PATCH v2 1/7] usb: dwc3-omap: use device_for_each_child to handle child removal Kishon Vijay Abraham I
2012-10-01 10:25 ` [PATCH v2 2/7] usb: dwc3-omap: use of_platform API to create dwc3 core pdev Kishon Vijay Abraham I
2012-10-01 10:25 ` [PATCH v2 3/7] usb: dwc3-omap: use runtime API's to enable clocks Kishon Vijay Abraham I
2012-10-01 10:25 ` [PATCH v2 4/7] usb: dwc3-omap: Remove explicit writes to SYSCONFIG register Kishon Vijay Abraham I
2012-10-01 10:25 ` [PATCH v2 5/7] usb: dwc3-omap: Add an API to write to dwc mailbox Kishon Vijay Abraham I
2012-10-01 10:25 ` [PATCH v2 6/7] usb: dwc3-omap: Minor fixes to get dt working Kishon Vijay Abraham I
2012-10-01 18:00 ` Sergei Shtylyov [this message]
2012-10-01 10:25 ` [PATCH v2 7/7] usb: dwc3: core: add dt support for dwc3 core Kishon Vijay Abraham I
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=5069DA49.7030901@mvista.com \
--to=sshtylyov@mvista.com \
--cc=balbi@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
/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