From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] Severals questions How to submit new u-boot features
Date: Fri, 03 Sep 2010 20:01:21 +0200 [thread overview]
Message-ID: <4C8137F1.3030906@free.fr> (raw)
In-Reply-To: <0B9F1C5B86169C4EA9D042C251022E49105CD81DDA@SAFEX1MAIL3.st.com>
Hi,
Le 03/09/2010 19:06, Christophe Henri RICARD a ?crit :
> Hi,
>
> I am actually working to add a new driver to u-boot related to Trusted Platform Module (TPM) for embedded system. (On a u-boot version 2009.11)
> I would be interested to know:
>
> - what is the process to do the submission ?
Read up <http://www.denx.de/wiki/U-Boot/Patches>
> - Because the available i2c interfaces looks to be only for i2c memory (such as eeprom memory), I had to rework some i2c interfaces to be able to send directly my TPM command/data through the i2c bus. This mean write or read some data directly on the i2c bus without sending any offset byte.
You can do that with the current i2c drivers by making sure that adrlen=0.
> Will it be acceptable for the community to add those two new interfaces (i2c_write_direct/i2c_read_direct) for each i2c driver ?
I would think they are unneeded, see the adrlen=0 trick. (If I were to
suggest an I2C overhaul [hi Heiko :)], I'd rather suggest adding a
generic i2c transaction API which would allow mixing elementary writes
and reads with optional STARTs and STOPs inbetween).
> - Is there any coding style specification ?
Look up <>http://www.denx.de/wiki/U-Boot/CodingStyle> (actually many
topics are covered, see left column).
> Thanks for your help
np :)
> Best Regards
> Christophe RICARD
> STMicroelectronics.
Amicalement,
--
Albert.
prev parent reply other threads:[~2010-09-03 18:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 17:06 [U-Boot] Severals questions How to submit new u-boot features Christophe Henri RICARD
2010-09-03 18:01 ` Albert ARIBAUD [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=4C8137F1.3030906@free.fr \
--to=albert.aribaud@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox