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?



regards,


Lucas

On 26-02-2014 11:50, Alexander Shiyan wrote:

Среда, 26 февраля 2014, 10:12 -03:00 от Lucas Zampar Bernardi [off-list ref]:

quoted

Hello Alexander,


Follow attach my DTS file and my dmesg log.
How you can see, we have "mcp251x: probe of spi32766.2 failed with error
-2.".
I discovered that the cause is the clock config structure, because if
I've forced a frequency hardcode all driver works.
The point where I've forced is:

...

Seems, you are missing "fixed-clock" driver in the kernel.
Is CONFIG_COMMON_CLK option is enabled in your .config?

---