From: ipaton0@gmail.com (Iain Paton)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] imx6: imx6duallite/solo i2c4 clock
Date: Wed, 16 Apr 2014 19:33:06 +0100 [thread overview]
Message-ID: <534ECCE2.1060006@gmail.com> (raw)
In-Reply-To: <20140416074712.GK2523@dragon>
On 16/04/14 08:47, Shawn Guo wrote:
> On Tue, Apr 15, 2014 at 10:15:15AM +0100, Iain Paton wrote:
>> I'm working on a board using the imx6solo that implements i2c4 and while
>> building the devicetree it became clear that the devicetree fragment for
>> i2c4 in imx6dl.dtsi it's missing the necessary clock.
>>
>> Investigating further turned up that the ecspi5 clock in CCM_CCGR1 on the
>> quad/dual is replaced with the i2c4 clock on duallite/solo.
>>
>> Would the following patch be sufficient to allow correct use of this clock?
>
> Yes, Iain. It looks correct to me. Care to send a formal patch for it?
Sure, it's on it's way.
prev parent reply other threads:[~2014-04-16 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 9:15 [RFC PATCH] imx6: imx6duallite/solo i2c4 clock Iain Paton
2014-04-16 7:47 ` Shawn Guo
2014-04-16 18:33 ` Iain Paton [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=534ECCE2.1060006@gmail.com \
--to=ipaton0@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).