linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: cgagneraud@techworks.ie (Christian Gagneraud)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ep93xx: introduce clk parent
Date: Fri, 09 Oct 2009 18:11:21 +0100	[thread overview]
Message-ID: <4ACF6EB9.1010509@techworks.ie> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE190901DB7CE4@mi8nycmail19.Mi8.com>

H Hartley Sweeten wrote:
> On Thursday, October 08, 2009 4:15 PM, Christian Gagneraud wrote:
>> Hartley,
>>
>> The keypad clock is already in as is the et_keytchclk_rate too.
> 
> Saw that.  Already responded to you about it.
> 
>> Can you explain me by the way why the keypad declares the clock with 
>> dev_id="ep93xx-keypad" and no con_id, but the pwm declares the clock 
>> with no dev_id and with con_id="clk_pwm"
>> Which of dev and con is the consumer and which one is the producer?
>> I'm a bit confuse between the platform_driver.name, the clock.dev_id 
>> and the clock.con_id
>>
>> As well I've noticed that the EP93XX keypad input driver does a 
>> clock_get("clk_key"), but this clock doesn't exist. or did I miss 
>> something.
> 
> No, I did...
> 
> When the input group picked up the keypad driver I didn't get the core
> support files reviewed/merged.  So basically the keypad driver is
> currently broken.
> 
> Patch 5578/1 was the first patch needed to fix this.  During the review
> for it, the original use intended for by the driver changed.  So I'm in
> the process of fixing the keypad driver.  Hopefully I'll get this all
> resolved soon.
> 
> As far as the dev/con id's.
> 
> I could have created two clocks for the pwms.  One for dev_id="pwm.0" and
> one for dev_id="pwm.1" which is how the two pwm ports get identified when
> used.  But, since the pwm clock cannot be disabled it seemed cleaner to
> just add one clock, con_id="clk_pwm", since the clock is common for both
> pwm controllers.  Look at drivers/misc/ep93xx_pwm.c and you will see that
> the clk_get() call passes the dev_id and the con_id.  Since there is not
> a matching dev_id in the ep93xx clocks[], the match occurs based on the
> con_id.

OK, I'll do that.

I've noticed as well that there's missing bits from Matthieu's 
0024-ep93xx_pwm.patch, that's almost nothing, but I guess that was the 
main reason Matthieu added PWM support to EP93XX:

diff --git a/arch/arm/mach-ep93xx/ts72xx.c b/arch/arm/mach-ep93xx/ts72xx.c
index 086d069..ee7baeb 100644
--- a/arch/arm/mach-ep93xx/ts72xx.c
+++ b/arch/arm/mach-ep93xx/ts72xx.c
@@ -303,6 +303,9 @@ static void __init ts72xx_init_machine(void)
         spi_register_board_info(ts72xx_spi_bus, 
ARRAY_SIZE(ts72xx_spi_bus));
         #endif

+       /* PWM1 is DIO_6 on TS-72xx header */
+       ep93xx_register_pwm(1, 1);
+
         ep93xx_register_eth(&ts72xx_eth_data, 1);
  }

> 
> Make sense?

Yes it does! :)

Regards,
Chris

> 
> Regards,
> Hartley

  reply	other threads:[~2009-10-09 17:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 22:57 [PATCH] ep93xx: introduce clk parent H Hartley Sweeten
2009-09-23 22:48 ` H Hartley Sweeten
2009-09-30 19:53   ` Ryan Mallon
2009-09-30 21:30     ` H Hartley Sweeten
2009-10-01 14:59       ` Russell King - ARM Linux
2009-10-01 16:32         ` H Hartley Sweeten
2009-10-08 21:28           ` Christian Gagneraud
2009-10-08 21:34             ` Russell King - ARM Linux
2009-10-08 22:09               ` Christian Gagneraud
2009-10-08 23:05                 ` H Hartley Sweeten
2009-10-08 22:32               ` H Hartley Sweeten
2009-10-08 22:38                 ` Russell King - ARM Linux
2009-10-08 22:45                   ` H Hartley Sweeten
2009-10-08 22:40             ` H Hartley Sweeten
2009-10-08 23:14               ` Christian Gagneraud
2009-10-08 23:25                 ` H Hartley Sweeten
2009-10-09 17:11                   ` Christian Gagneraud [this message]
2009-10-09 17:30                     ` H Hartley Sweeten

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=4ACF6EB9.1010509@techworks.ie \
    --to=cgagneraud@techworks.ie \
    --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).