From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Marek Roszko <mark.roszko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: ludovic.desroches-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2] i2c:at91: Add device tree property to set clock-frequency
Date: Mon, 10 Mar 2014 17:29:55 +0100 [thread overview]
Message-ID: <20140310162955.GF11592@katana> (raw)
In-Reply-To: <1393293045-31849-1-git-send-email-mark.roszko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
> @@ -711,6 +711,7 @@ static int at91_twi_probe(struct platform_device *pdev)
> struct resource *mem;
> int rc;
> u32 phy_addr;
> + int bus_clk_rate;
>
> dev = devm_kzalloc(&pdev->dev, sizeof(*dev), GFP_KERNEL);
> if (!dev)
> @@ -756,7 +757,12 @@ static int at91_twi_probe(struct platform_device *pdev)
> dev->use_dma = true;
> }
>
> - at91_calc_twi_clock(dev, TWI_CLK_HZ);
> + rc = of_property_read_u32(dev->dev->of_node, "clock-frequency",
> + &bus_clk_rate);
The function is named read_u32, so the variable used should be u32.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-03-10 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 1:50 [PATCH v2] i2c:at91: Add device tree property to set clock-frequency Marek Roszko
[not found] ` <1393293045-31849-1-git-send-email-mark.roszko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-02-28 11:05 ` Ludovic Desroches
2014-03-06 13:48 ` Mark Roszko
2014-03-07 3:51 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <4A1E236E-E048-4E37-AFE8-C0AC283B73D0-sclMFOaUSTBWk0Htik3J/w@public.gmane.org>
2014-03-07 4:26 ` Mark Roszko
2014-03-07 5:08 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <05EF9B59-7009-49D2-B57F-5612C39F1FF0-sclMFOaUSTBWk0Htik3J/w@public.gmane.org>
2014-03-07 5:30 ` Mark Roszko
2014-03-10 16:29 ` Wolfram Sang [this message]
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=20140310162955.GF11592@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ludovic.desroches-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org \
--cc=mark.roszko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).