public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Pantelic <vladoman@gmail.com>
To: "Enric Balletbò i Serra" <eballetbo@gmail.com>
Cc: linux-omap@vger.kernel.org, linux-arm@vger.kernel.org
Subject: Re: [RFC] About ARM expansion boards and others things
Date: Wed, 04 May 2011 12:28:41 +0200	[thread overview]
Message-ID: <4DC12A59.2010608@gmail.com> (raw)
In-Reply-To: <BANLkTimjWtqLsWA1Gthix6RZYMzNRdC7rg@mail.gmail.com>

Enric Balletbò i Serra wrote:
> Hi guys,
> I'm thinking probably in a crazy idea, I hope someone can help me or
> kill definitely this idea from my mind.
>
> I'll explain a little more, the real problem is I don't know how to
> add support for an expansion board for IGEP v2 board. I see most of
> boards adds the support inside the board-xxxxx.c file, for example if
> the expansion board has a Touchscreen interface using ADS7846/TSC2046
> they register ads7846 platform data in board-xxxx.c file. This is ok
> beacause the ads7846 can be detected and if expansion board is not
> present  the detection fails, but maybe other devices in expansion
> board can't be detected (for example an I/O expansion). So which is
> the best form to do this ?
>
> I'm thinking in create a kernel module for the expansion board that
> add all the new features, the expansion board should come with a I2C
> E2PROM for board ID storage, so the idea is create an i2c driver that
> reads the E2PROM and if found the Board ID inits all the expansion
> board devices.

don't know if you are aware of that:

http://elinux.org/BeagleBoardPinMux#Expansion_boards

also beagle.c board file has support for some expansion boards
already, maybe there is some code to be shared.

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2011-05-04 10:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-03 17:25 [RFC] About ARM expansion boards and others things Enric Balletbò i Serra
2011-05-04  9:27 ` Tony Lindgren
2011-05-04 10:28 ` Vladimir Pantelic [this message]
2011-05-04 10:46   ` Enric Balletbò i Serra
2011-05-04 11:44     ` Koen Kooi
2011-05-04 10:53 ` Igor Grinberg
2011-05-04 11:20   ` Igor Grinberg
2011-05-04 12:28   ` Enric Balletbò i Serra
2011-05-04 13:17     ` Igor Grinberg
2011-05-04 11:50 ` Tomi Valkeinen

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=4DC12A59.2010608@gmail.com \
    --to=vladoman@gmail.com \
    --cc=eballetbo@gmail.com \
    --cc=linux-arm@vger.kernel.org \
    --cc=linux-omap@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox