From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wolfram Sang Subject: Re: [RFC: PATCH v5] i2c: exynos5: add High Speed I2C controller driver Date: Tue, 26 Mar 2013 10:23:07 +0100 Message-ID: <20130326092306.GA8553@the-dreams.de> References: <1363062732-27869-1-git-send-email-ch.naveen@samsung.com> <1363796690-30242-1-git-send-email-ch.naveen@samsung.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-samsung-soc-owner@vger.kernel.org To: Yuvaraj CD Cc: Naveen Krishna Chatradhi , linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org, w.sang@pengutronix.de, khali@linux-fr.org, ben-linux@fluff.org, grant.likely@secretlab.ca, devicetree-discuss@lists.ozlabs.org, sjg@chromium.org, grundler@chromium.org, naveenkrishna.ch@gmail.com, broonie@opensource.wolfsonmicro.com List-Id: devicetree@vger.kernel.org > > + /* CLK_DIV max is 256 */ > > + for (i = 0; i < 256; i++) { > > + utemp1 = utemp0 / (i + 1); > > + /* SCLK_L/H max is 256 / 2 */ > > + if (utemp1 < 128) { > I think TSCLK_L and TSCLK_H both can be configured upto 255.Why > limiting it to < 128 ? > By limiting it to < 128 dont we achieve lesser SCL clock? Thanks for reviewing but please quote only the relevant part of the message (like I did). This improves readability a lot.