All of lore.kernel.org
 help / color / mirror / Atom feed
From: ppokorny@penguincomputing.com (Phil Pokorny)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Add McSPI devices found in AM33xx SoC to dtsi
Date: Tue, 9 Oct 2012 07:24:28 -0700	[thread overview]
Message-ID: <3608180472966131184@unknownmsgid> (raw)
In-Reply-To: <518397C60809E147AF5323E0420B992E3E9CA61C@DBDE01.ent.ti.com>

On Oct 9, 2012, at 3:36 AM, "Philip, Avinash" <avinashphilip@ti.com>
wrote:

> On Tue, Oct 09, 2012 at 10:40:58, Phil Pokorny wrote:
>> We're using the BeagleBone for a project and we need the SPI devices
>> available and configured with all available chip selects.
>>
>> Please accept the following patch to add these to the base .dtsi file
>> so they can then be enabled in the beaglebone specific .dts with
>> minimal fuss.
>
> Patch for adding MCSPI in am33xx.dtsi already been sent by me.
> https://lkml.org/lkml/2012/9/18/32

Thank you for responding.

Was that accepted?  It didn't seem to be in the Linux-omap git tree I
cloned. I need to check the Torvalds mainline kernel.

I believe the number of chip selects on spi1 is incorrect. There is
only one (1) CS shown in the hardware documentation for AM33xx.

Is OMAP4-McSPI the best match for the hardware?  The mcspi driver
appears to differ only in the register offset used.  A hard coded zero
value for omap2 and a named constant for omap4. The hardware manual
for the AM33xx shows the register map starting at zero.

Thank you,
Phil P.
>

  reply	other threads:[~2012-10-09 14:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09  5:10 [PATCH] Add McSPI devices found in AM33xx SoC to dtsi Phil Pokorny
2012-10-09 10:35 ` Philip, Avinash
2012-10-09 14:24   ` Phil Pokorny [this message]
2012-10-10  4:09     ` Philip, Avinash
2012-10-10 12:01     ` Hebbar, Gururaja

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=3608180472966131184@unknownmsgid \
    --to=ppokorny@penguincomputing.com \
    --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 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.