From: Wolfram Sang <w.sang@pengutronix.de>
To: Roland Stigge <stigge@antcom.de>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <robherring2@gmail.com>,
vitalywool@gmail.com, khali@linux-fr.org, ben-linux@fluff.org,
rob.herring@calxeda.com, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, arm@kernel.org,
linux-arm-kernel@lists.infradead.org, kevin.wells@nxp.com,
srinivas.bakki@nxp.com
Subject: Re: [PATCH v4] i2c: Add device tree support to i2c-pnx.c
Date: Fri, 20 Apr 2012 09:28:11 +0200 [thread overview]
Message-ID: <20120420072811.GA9769@pengutronix.de> (raw)
In-Reply-To: <4F90812F.5090106@antcom.de>
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
> Another solution would be to not use timeout with the dt enabled
> i2c-pnx for now (using the hard coded default timeout as the current
> i2c-pnx.c does) and possibly introduce the (anyway optional) "timeout"
> later.
Yeah, let's do it like this.
> Interesting! When the documentation is outdated - how does the parser
> actually decide between hex (e.g. regs/addresses) and dec (e.g.
> clock-frequency) in the absence of "0x"?
Are there regs without 0x?
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-04-20 7:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 15:50 [PATCH v4] i2c: Add device tree support to i2c-pnx.c Roland Stigge
2012-04-19 16:07 ` Wolfram Sang
2012-04-19 16:32 ` Roland Stigge
2012-04-19 20:39 ` Wolfram Sang
2012-04-19 21:18 ` Roland Stigge
2012-04-20 7:28 ` Wolfram Sang [this message]
2012-04-20 7:53 ` Roland Stigge
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=20120420072811.GA9769@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=arm@kernel.org \
--cc=ben-linux@fluff.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=kevin.wells@nxp.com \
--cc=khali@linux-fr.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=robherring2@gmail.com \
--cc=srinivas.bakki@nxp.com \
--cc=stigge@antcom.de \
--cc=vitalywool@gmail.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