From: "Cousson, Benoit" <b-cousson@ti.com>
To: Sourav <sourav.poddar@ti.com>
Cc: <linux-omap@vger.kernel.org>,
<devicetree-discuss@lists.ozlabs.org>,
<linux-kernel@vger.kernel.org>, Felipe Balbi <balbi@ti.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: Re: [RESEND/PATCHv3] arm: dts: omap5-evm: Add keypad support
Date: Tue, 30 Oct 2012 10:13:34 +0100 [thread overview]
Message-ID: <508F9A3E.9020105@ti.com> (raw)
In-Reply-To: <508F64EC.9000809@ti.com>
Hi Sourav,
On 10/30/2012 6:26 AM, Sourav wrote:
> Hi Benoit,
> On Monday 29 October 2012 10:14 PM, Benoit Cousson wrote:
>> Hi Sourav,
>>
>> On 10/29/2012 11:40 AM, Sourav Poddar wrote:
>>> Add keypad data node in omap5-evm.
>>>
>>> Based on I2C support patch for omap5, which has been
>>> already posted as a different series.
>>>
>>> Tested on omap5430 evm with 3.7-rc1 kernel.
>>>
>>> Cc: Felipe Balbi <balbi@ti.com>
>>> Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
>>>
>>> Tested on omap5430 sdp with 3.7-rc1 kernel.
>>>
>>> Signed-off-by: Sourav Poddar <sourav.poddar@ti.com>
>>> ---
>>> arch/arm/boot/dts/omap5-evm.dts | 95
>>> +++++++++++++++++++++++++++++++++++++++
>>> 1 files changed, 95 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/arch/arm/boot/dts/omap5-evm.dts
>>> b/arch/arm/boot/dts/omap5-evm.dts
>>> index c663eba..b812d6d 100644
>>> --- a/arch/arm/boot/dts/omap5-evm.dts
>>> +++ b/arch/arm/boot/dts/omap5-evm.dts
>>> @@ -140,3 +140,98 @@
>>> &mcbsp3 {
>>> status = "disabled";
>>> };
>>> +
>>> +&i2c5 {
>>> + clock-frequency = <400000>;
>>> +
>>> + smsc@38 {
>>> + compatible = "smscece1099";
>>> + reg = <0x38>;
>>> + clock = <0x13>;
>> What does that "clock" mean?
> This chip supports a clock control register which is used to enable the
> interface used by the chip to communicate. Here, the interface which you
> can are
> SMBUS interface or BC-LINK interface.
OK, so you should use a less generic name than "clock" and potentially
prefix it with "smsc," since it is not a generic attribute at all.
BTW, cannot we use the CCF in order to control that clock? I guess it is
just a clock mux?
Well, anyway we need CCF for OMAP to be merged first :-)
But it might worth highlighting this is a temporary solution.
>> I cannot find that in the binding documentation. BTW, did you add that
>> documentation in the driver patch?
> Nope, I missed out on the dt binding documentation for the driver. :(
>
> Will send a seperate patch for the bindings.
Thanks,
Benoit
next prev parent reply other threads:[~2012-10-30 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 10:40 Sourav Poddar
2012-10-29 16:18 ` Felipe Balbi
2012-10-29 16:44 ` Benoit Cousson
2012-10-30 5:26 ` Sourav
2012-10-30 9:13 ` Cousson, Benoit [this message]
2012-10-30 9:36 ` Sourav
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=508F9A3E.9020105@ti.com \
--to=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=sourav.poddar@ti.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
Powered by JetHome