From: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
To: Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"Detlev Zundel" <dzu-ynQEQJNshbs@public.gmane.org>,
"Dong Aisheng" <b29396-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
"Fabio Estevam"
<fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
"Linux ARM kernel"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"Sascha Hauer" <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
"Stefano Babic" <sbabic-ynQEQJNshbs@public.gmane.org>,
"Uwe Kleine-König"
<u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
"Wolfgang Denk" <wd-ynQEQJNshbs@public.gmane.org>,
"Wolfram Sang" <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Subject: Re: [PATCH 1/2 V3] MXS: Set I2C timing registers for mxs-i2c
Date: Mon, 11 Jun 2012 12:53:17 +0200 [thread overview]
Message-ID: <201206111253.17314.marex@denx.de> (raw)
In-Reply-To: <20120611073036.GG2552-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
Dear Shawn Guo,
> On Sun, Jun 10, 2012 at 01:53:05PM +0200, Marek Vasut wrote:
> > > +struct mxs_i2c_speed_config {
> > > + uint32_t timing0;
> > > + uint32_t timing1;
> > > + uint32_t timing2;
> > > +};
> > > +
> > > +/* Timing values for the default 24MHz clock supplied into the i2c
> > > block.
> >
> > Thinking about these further -- does anyone have any idea how these
> > numbers were derived? And possibly even formula for that?
> >
> > And maybe we should somehow make sure the source runs on 24MHz (how?).
>
> There is nothing about I2C clock mentioned in CLKCTRL chapter. I just
> contacted design team and was told that I2C clock sources from APBX
> (xbus) clock and always runs at the same frequency there.
Ok, then can you please try asking them how to exactly compute the values in
timing0-timing2 registers? So we don't have to hardcode them like it's done now?
Best regards,
Marek Vasut
WARNING: multiple messages have this Message-ID (diff)
From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2 V3] MXS: Set I2C timing registers for mxs-i2c
Date: Mon, 11 Jun 2012 12:53:17 +0200 [thread overview]
Message-ID: <201206111253.17314.marex@denx.de> (raw)
In-Reply-To: <20120611073036.GG2552@S2101-09.ap.freescale.net>
Dear Shawn Guo,
> On Sun, Jun 10, 2012 at 01:53:05PM +0200, Marek Vasut wrote:
> > > +struct mxs_i2c_speed_config {
> > > + uint32_t timing0;
> > > + uint32_t timing1;
> > > + uint32_t timing2;
> > > +};
> > > +
> > > +/* Timing values for the default 24MHz clock supplied into the i2c
> > > block.
> >
> > Thinking about these further -- does anyone have any idea how these
> > numbers were derived? And possibly even formula for that?
> >
> > And maybe we should somehow make sure the source runs on 24MHz (how?).
>
> There is nothing about I2C clock mentioned in CLKCTRL chapter. I just
> contacted design team and was told that I2C clock sources from APBX
> (xbus) clock and always runs at the same frequency there.
Ok, then can you please try asking them how to exactly compute the values in
timing0-timing2 registers? So we don't have to hardcode them like it's done now?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-06-11 10:53 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-09 11:45 [PATCH 1/2 V3] MXS: Set I2C timing registers for mxs-i2c Marek Vasut
2012-06-09 11:45 ` Marek Vasut
[not found] ` <1339242351-8797-1-git-send-email-marex-ynQEQJNshbs@public.gmane.org>
2012-06-09 11:45 ` [PATCH 2/2 V2] MXS: Implement DMA support into mxs-i2c Marek Vasut
2012-06-09 11:45 ` Marek Vasut
2012-06-10 11:53 ` [PATCH 1/2 V3] MXS: Set I2C timing registers for mxs-i2c Marek Vasut
2012-06-10 11:53 ` Marek Vasut
[not found] ` <201206101353.06018.marex-ynQEQJNshbs@public.gmane.org>
2012-06-11 7:30 ` Shawn Guo
2012-06-11 7:30 ` Shawn Guo
[not found] ` <20120611073036.GG2552-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2012-06-11 10:53 ` Marek Vasut [this message]
2012-06-11 10:53 ` Marek Vasut
[not found] ` <201206111253.17314.marex-ynQEQJNshbs@public.gmane.org>
2012-06-11 14:42 ` Shawn Guo
2012-06-11 14:42 ` Shawn Guo
[not found] ` <20120611144237.GI2552-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2012-06-23 18:19 ` Marek Vasut
2012-06-23 18:19 ` Marek Vasut
2012-06-11 6:39 ` Shawn Guo
2012-06-11 6:39 ` Shawn Guo
[not found] ` <20120611063903.GD2552-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2012-06-11 10:54 ` Marek Vasut
2012-06-11 10:54 ` Marek Vasut
[not found] ` <201206111254.21766.marex-ynQEQJNshbs@public.gmane.org>
2012-06-27 1:30 ` Marek Vasut
2012-06-27 1:30 ` Marek Vasut
[not found] ` <201206270330.31669.marex-ynQEQJNshbs@public.gmane.org>
2012-06-27 2:13 ` Shawn Guo
2012-06-27 2:13 ` Shawn Guo
[not found] ` <20120627021336.GA9787-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2012-06-27 2:34 ` Marek Vasut
2012-06-27 2:34 ` Marek Vasut
2012-06-23 18:47 ` Marek Vasut
2012-06-23 18:47 ` Marek Vasut
[not found] ` <201206232047.33228.marex-ynQEQJNshbs@public.gmane.org>
2012-06-25 15:43 ` Shawn Guo
2012-06-25 15:43 ` Shawn Guo
[not found] ` <20120625154354.GC2342-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2012-06-25 16:02 ` Marek Vasut
2012-06-25 16:02 ` Marek Vasut
2012-06-27 1:15 ` Marek Vasut
2012-06-27 1:15 ` Marek Vasut
-- strict thread matches above, loose matches on Subject: below --
2012-07-09 16:22 Marek Vasut
2012-07-09 16:22 ` Marek Vasut
[not found] ` <1341850974-11977-1-git-send-email-marex-ynQEQJNshbs@public.gmane.org>
2012-07-13 8:07 ` Wolfram Sang
2012-07-13 8:07 ` Wolfram Sang
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=201206111253.17314.marex@denx.de \
--to=marex-ynqeqjnshbs@public.gmane.org \
--cc=b29396-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=dzu-ynQEQJNshbs@public.gmane.org \
--cc=fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=sbabic-ynQEQJNshbs@public.gmane.org \
--cc=shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=wd-ynQEQJNshbs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.