public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] dm: Add timeline and guide for porting serial drivers
Date: Sun, 20 Dec 2015 00:56:49 +0100	[thread overview]
Message-ID: <201512200056.49618.marex@denx.de> (raw)
In-Reply-To: <CAPnjgZ0iLha+rF3i8qhnRpf+S1BZ5XV9Y5=Fq9x=L-uQ1d=hWw@mail.gmail.com>

On Sunday, December 20, 2015 at 12:07:22 AM, Simon Glass wrote:
> Hi Marek,
> 
> On 13 December 2015 at 12:55, Marek Vasut <marex@denx.de> wrote:
> > On Friday, November 20, 2015 at 06:48:47 PM, Simon Glass wrote:
> >> Add a README with a brief guide to porting serial drivers over to use
> >> driver model.
> >> 
> >> Add a timeline also. All serial drivers should be converted by the end
> >> of January 2016.
> >> 
> >> Signed-off-by: Simon Glass <sjg@chromium.org>
> >> ---
> >> To avoid anyone missing out on this, I have added to Cc the all U-Boot
> >> maintainers using this:
> >> 
> >> (for f in $(find . -name MAINTAINERS); do grep ^M: $f; done) | \
> >> 
> >>       awk '{$1=""; print "Series-cc:" $0}' |sort | uniq
> >> 
> >> This is about 229 email address, of which 217 seem to be different
> >> people.
> >> 
> >> Changes in v3:
> >> - Fix the date to avoid time machine issues
> >> 
> >> Changes in v2:
> >> - Copy the patch to all maintainers
> >> - Move the timeline back to January
> >> 
> >>  doc/driver-model/serial-howto.txt | 58
> >> 
> >> +++++++++++++++++++++++++++++++++++++++ 1 file changed, 58 insertions(+)
> >> 
> >>  create mode 100644 doc/driver-model/serial-howto.txt
> >> 
> >> diff --git a/doc/driver-model/serial-howto.txt
> >> b/doc/driver-model/serial-howto.txt new file mode 100644
> >> index 0000000..60483a4
> >> --- /dev/null
> >> +++ b/doc/driver-model/serial-howto.txt
> >> @@ -0,0 +1,58 @@
> >> +How to port a serial driver to driver model
> >> +===========================================
> >> +
> >> +About 16 of 33 serial drivers have been converted as at September 2015.
> >> It +is time for maintainers to start converting over the remaining
> >> serial drivers: +
> >> +   altera_jtag_uart.c
> >> +   altera_uart.c
> > 
> > These are probably already converted.
> > 
> >> +   arm_dcc.c
> >> +   lpc32xx_hsuart.c
> >> +   mcfuart.c
> >> +   mxs_auart.c
> > 
> > ^ This system does not use DM at all.
> > 
> >> +   opencores_yanu.c
> >> +   serial_bfin.c
> >> +   serial_imx.c
> > 
> > DTTO
> > 
> >> +   serial_lpuart.c
> >> +   serial_max3100.c
> >> +   serial_pxa.c
> > 
> > DTTO
> > 
> >> +   serial_s3c24x0.c
> > 
> > DTTO
> > 
> >> +   serial_sa1100.c
> > 
> > This driver is probably dead code
> > 
> >> +   serial_stm32.c
> >> +   serial_xuartlite.c
> >> +   usbtty.c
> >> +
> >> +You should complete this by the end of January 2016.
> > 
> > So what do you suggest to do with boards which do not use DM at all ?
> 
> I'd say move them over...

That's not doable this late in the RC cycle though. I would suggest to postpone
the date.

  reply	other threads:[~2015-12-19 23:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 17:48 [U-Boot] [PATCH v3] dm: Add timeline and guide for porting serial drivers Simon Glass
2015-11-20 22:47 ` Tom Rini
2015-12-13 19:55 ` Marek Vasut
2015-12-19 23:07   ` Simon Glass
2015-12-19 23:56     ` Marek Vasut [this message]
2015-12-20  2:40       ` Simon Glass
2015-12-20  2:57         ` Marek Vasut

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=201512200056.49618.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