Tnks a lot guys!

I will check for COMMON_CLK support at linux-at91, but for while, I will 
use the hardcode frequency!

regards,

lucas

On 26-02-2014 15:01, Alexander Shiyan wrote:

Среда, 26 февраля 2014, 18:50 +01:00 от Marc Kleine-Budde [off-list ref]:

quoted

On 02/26/2014 06:36 PM, Lucas Zampar Bernardi wrote:

quoted

You are right Alexander!
The CONFIG_COMMON_CLK hasn't enable!
But for all SOC AT91_SAM9x5 still uses old clock style (AT91_USE_OLD_CLK):

config SOC_AT91SAM9X5
         bool "AT91SAM9x5 family"
         select HAVE_AT91_DBGU0
         select HAVE_FB_ATMEL
         select SOC_AT91SAM9
         select AT91_USE_OLD_CLK
         select HAVE_AT91_UTMI
         select HAVE_AT91_SMD
         select HAVE_AT91_USB_CLK

and one of dependencies for COMMON_CLK_AT91 is don't be AT91_USE_OLD_CLK

config COMMON_CLK_AT91
         bool
        default AT91_PMC_UNIT && USE_OF && !AT91_USE_OLD_CLK
         select COMMON_CLK

config OLD_CLK_AT91
         bool
         default AT91_PMC_UNIT && AT91_USE_OLD_CLK




Now came my question: Can I use CONFIG_COMMON_CLK without my ARCH
support? If not, how we will support devices that need CONFIG_COMMON_CLK?

You probably have to wait for common clock support. However you can
still hook platform data to your spi device. For a mxs add this to
arch/arm/mach-mxs/mach-mxs.c:

static int abc_spi_notifier_call(struct notifier_block *nb,
					unsigned long event, void *data)

...

Nevertheless, support for the CLK API for SOC AT91_SAM9x5 seems
already in the kernel.
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/drivers/clk/at91/pmc.c?id=05202872ca98f8ea61943a9b530417c5503b816f

You can ask about the CLK status in the AT91 mailing list.

---