From: Lucas Zampar Bernardi <lucas.zampar@gmail.com>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>, linux-can@vger.kernel.org
Subject: Re: MCP2515 DTS support
Date: Wed, 26 Feb 2014 14:36:44 -0300 [thread overview]
Message-ID: <530E262C.2040603@gmail.com> (raw)
In-Reply-To: <1393426239.267518204@f362.i.mail.ru>
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 <lucas.zampar@gmail.com>:
>> 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?
>
> ---
next prev parent reply other threads:[~2014-02-26 17:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1445543c688.2748.cbaa067694a7e68fb76a213b35423fb5@gmail.com>
2014-02-21 16:26 ` MCP2515 DTS support Lucas Zampar Bernardi
2014-02-22 19:46 ` Lucas Zampar Bernardi
2014-02-25 21:35 ` Marc Kleine-Budde
2014-02-26 4:17 ` Alexander Shiyan
2014-02-26 13:12 ` Lucas Zampar Bernardi
2014-02-26 14:50 ` Alexander Shiyan
2014-02-26 17:36 ` Lucas Zampar Bernardi [this message]
2014-02-26 17:50 ` Marc Kleine-Budde
2014-02-26 18:01 ` Alexander Shiyan
2014-02-26 18:17 ` Lucas Zampar Bernardi
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=530E262C.2040603@gmail.com \
--to=lucas.zampar@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=shc_work@mail.ru \
/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).