From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH v2 0/14] Driver model implementation, tests, demo and GPIO
Date: Fri, 17 May 2013 07:08:22 +0200 [thread overview]
Message-ID: <201305170708.22810.marex@denx.de> (raw)
In-Reply-To: <CAPnjgZ1HW-qU8bNeuExUQPuHfXr6VU4ZKSTPdCZuFjHnc+wiSA@mail.gmail.com>
Dear Simon Glass,
> Hi,
>
> On Tue, May 7, 2013 at 12:41 PM, Simon Glass <sjg@chromium.org> wrote:
> > Note: If you are reviewing this code, but don't have a lot of time,
> > please consider starting with the 'demo' driver (patch 'dm: Add a
> > demonstration/example driver') since it clearly shows how devices and
> > uclasses work. Much of this series consists of test code and plumbing, so
> > is of less interest to driver authors.
> >
> > This patch adds a driver model implementation. It is taken from
> >
> > the driver model code developed by:
> > Marek Vasut <marex@denx.de>
> > Pavel Herrmann <morpheus.ibis@gmail.com>
> > Viktor K?iv?k <viktor.krivak@gmail.com>
> > Tomas Hlavacek <tmshlvck@gmail.com>
> >
> > Please see doc/driver-model/README.txt for details of how to run this and
> > what to look for. So far the documentation in doc/driver-model has not
> > been updated.
> >
> > You can find a test version of the code used here in branch dm2 at:
> > http://git.denx.de/u-boot-x86.git
> >
> > (Branch dm contains the original implementation)
>
> Does anyone have any comments on this series please?
I really cannot focus on much until 11th next month, sorry.
I should be able to review it after then ...
Best regards,
Marek Vasut
prev parent reply other threads:[~2013-05-17 5:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 19:41 [U-Boot] [RFC PATCH v2 0/14] Driver model implementation, tests, demo and GPIO Simon Glass
2013-05-07 19:41 ` [U-Boot] [RFC PATCH v2 01/14] sandbox: Make map_to_sysmem() use a constant pointer Simon Glass
2013-05-07 19:41 ` [U-Boot] [RFC PATCH v2 02/14] sandbox: Correct data sizes and printf() strings in fdtdec.c Simon Glass
2013-05-07 19:41 ` [U-Boot] [RFC PATCH v2 03/14] sandbox: config: Don't use 64-bit physical memory Simon Glass
2013-05-07 19:42 ` [U-Boot] [RFC PATCH v2 04/14] Add cmd_process_error() to report and process errors Simon Glass
2013-05-07 19:42 ` [U-Boot] [RFC PATCH v2 05/14] sandbox: config: Enable driver model Simon Glass
2013-05-07 19:42 ` [U-Boot] [RFC PATCH v2 06/14] dm: Add base driver model support Simon Glass
2013-05-07 19:42 ` [U-Boot] [RFC PATCH v2 07/14] dm: Set up driver model after relocation Simon Glass
2013-05-07 19:42 ` [U-Boot] [RFC PATCH v2 08/14] dm: Add basic tests Simon Glass
2013-05-07 19:42 ` [U-Boot] [RFC PATCH v2 09/14] dm: Add a 'dm' command for testing Simon Glass
2013-05-07 19:42 ` [U-Boot] [RFC PATCH v2 10/14] dm: Add a demonstration/example driver Simon Glass
2013-05-07 19:42 ` [U-Boot] [RFC PATCH v2 11/14] dm: Add GPIO support and tests Simon Glass
2013-05-07 19:42 ` [U-Boot] [RFC PATCH v2 12/14] sandbox: Convert GPIOs to use driver model Simon Glass
2013-05-07 19:42 ` [U-Boot] [RFC PATCH v2 13/14] dm: Enable gpio command to support " Simon Glass
2013-05-07 19:42 ` [U-Boot] [RFC PATCH v2 14/14] dm: Add README for " Simon Glass
2013-05-17 4:17 ` [U-Boot] [RFC PATCH v2 0/14] Driver model implementation, tests, demo and GPIO Simon Glass
2013-05-17 5:08 ` Marek Vasut [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=201305170708.22810.marex@denx.de \
--to=marex@denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox