From: Dieter Kiermaier <dk-arm-linux@gmx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Marvell Kirkwood newbie question GPIO functions
Date: Fri, 19 Jun 2009 10:47:02 +0200 [thread overview]
Message-ID: <200906191047.02750.dk-arm-linux@gmx.de> (raw)
In-Reply-To: <73173D32E9439E4ABB5151606C3E19E201D8E629C4@SC-VEXCH1.marvell.com>
Hi Prafulla,
>
> It's my pleasure to reply you :-)
> Basic Kirkwood Soc Support patches are available on the u-boot-arm.git/next
> (will be mainlined soon) Sheevaplug board support patches are also
> submitted those are under review, you can find them here...
> http://lists.denx.de/pipermail/u-boot/2009-June/054313.html
> http://lists.denx.de/pipermail/u-boot/2009-June/054314.html
> http://lists.denx.de/pipermail/u-boot/2009-June/054316.html
>
> Some other board patches are in pipeline
thanks very much for your help.
So far I have seen that marvell git u-boot is used to push it to mainline.
Great job!
What patches are in the pipeline?
>
> > Currently I'm using the u-boot from git.marvell.com which has
> > first board support for sheevaplug. I'm working on a custom
> > hardware design but as a starting point the sheevaplug seems
> > to work well.
>
> Objective for U-boot at git.marvell.com is to maintain a usable copy of
> u-boot with all accepted/unaccepted patches at one place to support
> Kirkwood developers, but once all these patches are mainlined, this
> repository will be removed.
>
> > Sadly there is no generic gpio support - at least I couldn't find it.
> > Are there any plans to support a driver for this feature?
>
> BTW: what you want to do at u-boot level with GPIOs?
> Current Kirkwood drivers and board support does not need any specific GPIO
> driver, you can access registers directly to read/write GPIOs. But I think
> if this is a need in future, I will add gpio driver support. You can
> provide me your requirements too.
I'm working on a custom hardware using the sheevaplug as a starting point.
Hopefully end of summer I finish the hardware work and have my own board.
But I have some additional requirements. For example control some power
supplies for LCD, boot an FPGA, program a clock chip device and so on.
So my demands are:
- GPIO support (for programming the clock generator which has a simple serial
????????interface to clock in the configuration data)
????????Yeah, I know that I can setup the GPIOs by writing directly to the
registers,
????????but a gpio frameworks would be much nicer ;)
- SPI (from the TDM module) support which works independet
? from NAND flash and SD-Card
I have allready posted a query to arm-linux kernel mailing list and yesterday
evening I have talked with Lennert on IRC regarding SPI and linux .
The SPI interface is needed in u-boot to boot my lattice FPGA
which is configured as slave serial device (and later on in linux to drive a
touch controller).
There is allready a FPGA configuration framework inside u-boot
and I would like to integrate also a lattice FPGA into that. But to do this
I need SPI support.
>
> > I'm willing to contribute some code if someone guides me a bit?
>
> You are most welcomed....
> Pls feel free to raise your queries...
Here they are :)
Thanks,
Dieter
> Regards..
> Prafulla . .
>
> > Thanks in advance,
> > Dieter
> >
> > _______________________________________________
> > U-Boot mailing list
> > U-Boot at lists.denx.de
> > http://lists.denx.de/mailman/listinfo/u-boot
next prev parent reply other threads:[~2009-06-19 8:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 8:05 [U-Boot] Marvell Kirkwood newbie question GPIO functions Dieter Kiermaier
2009-06-19 8:18 ` Prafulla Wadaskar
2009-06-19 8:47 ` Dieter Kiermaier [this message]
2009-06-19 8:53 ` Dieter Kiermaier
2009-06-19 9:20 ` Prafulla Wadaskar
2009-06-19 9:46 ` Dieter Kiermaier
2009-06-19 9:51 ` Prafulla Wadaskar
2009-06-19 10:00 ` Dieter Kiermaier
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=200906191047.02750.dk-arm-linux@gmx.de \
--to=dk-arm-linux@gmx.de \
--cc=u-boot@lists.denx.de \
/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.