All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: "Michael C. Cambria" <mcc@fid4.com>
Cc: Varka Bhadram <varkabhadram@gmail.com>, linux-wpan@vger.kernel.org
Subject: Re: at86rf233 on BeagleBone Black
Date: Thu, 23 Apr 2015 16:59:53 +0200	[thread overview]
Message-ID: <20150423145952.GD9284@omega> (raw)
In-Reply-To: <5538F7E7.9020308@fid4.com>

On Thu, Apr 23, 2015 at 09:47:19AM -0400, Michael C. Cambria wrote:
> 
> 
> On 04/23/2015 05:37 AM, Alexander Aring wrote:
> >On Mon, Apr 20, 2015 at 02:04:48PM -0400, Michael C. Cambria wrote:
> >....
> >>&spi1 {
> >>         status = "okay";
> >>         pinctrl-names = "default";
> >>         pinctrl-0 = <&spi1_pins>;
> >>         at86rf233@0 {
> >>                 compatible = "atmel,at86rf233";
> >>                 spi-max-frequency = <500000>;
> >now I detect this here. Why such low clock? You should use a 7.5 Mhz
> >clock here not 500 Khz. I had some troubles with such a low clock and
> >fragmentation handling.
> >
> >Means:
> >
> >change it to "spi-max-frequency = <7500000>;"
> >
> >- Alex
> 
> The openlabs blog post [0] used 500 Khz:

I know and that's terrible...

This was tested when the driver was in a "bad" state.

- Alex

      reply	other threads:[~2015-04-23 14:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <551EDFCA.3070905@fid4.com>
2015-04-03 19:13 ` at86rf233 on BeagleBone Black Alexander Aring
2015-04-03 19:36   ` Alexander Aring
2015-04-14 15:06   ` Alexander Aring
2015-04-16 21:08     ` Michael C. Cambria
2015-04-17  3:26       ` Varka Bhadram
2015-04-17 13:28         ` Michael C. Cambria
2015-04-17 22:19           ` Alexander Aring
2015-04-20 18:04             ` Michael C. Cambria
2015-04-20 18:24               ` Alexander Aring
2015-04-21  7:23               ` "Thomas B. Rücker"
2015-04-22  6:57                 ` "Thomas B. Rücker"
2015-04-23  9:37               ` Alexander Aring
2015-04-23 13:47                 ` Michael C. Cambria
2015-04-23 14:59                   ` Alexander Aring [this message]

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=20150423145952.GD9284@omega \
    --to=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=mcc@fid4.com \
    --cc=varkabhadram@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.