mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 0/6] i.MX51 RDU1 and Babbage USB fixes
Date: Mon, 27 Aug 2018 09:49:39 +0200	[thread overview]
Message-ID: <20180827074939.wx7vzos7qg7o23hb@pengutronix.de> (raw)
In-Reply-To: <20180825210315.4661-1-andrew.smirnov@gmail.com>

On Sat, Aug 25, 2018 at 02:03:09PM -0700, Andrey Smirnov wrote:
> Everyone:
> 
> These patches are a number of fixes I came up with while looking into
> USB related problems on Babbage board.
> 
> Feedback is welcome!
> 
> Thanks,
> Andrey Smirnov
> 
> Andrey Smirnov (6):
>   clk: i.MX: Port Linux clock tree for i.MX51 and i.MX53
>   ARM: imx51-zii-rdu1: Swtich to using Linux clock tree
>   ARM: freescale-mx51-babbage: Swtich to using Linux clock tree
>   ARM: freescale-mx51-babbage: Add USBH1 PHY reset sequence
>   dts: imx51-babbage: Add USBH1 iomux configuration
>   ARM: imx51-zii-rdu1: Add USBH1,2 iomux configuration

do 4/6 - 6/6 depend on the first three? If not I would apply them
independently.

Sascha

> 
>  .../arm/boards/freescale-mx51-babbage/board.c |  35 ++
>  arch/arm/dts/imx51-babbage.dts                |  24 +
>  arch/arm/dts/imx51-zii-rdu1.dts               |  46 ++
>  arch/arm/mach-imx/Kconfig                     |   2 +
>  drivers/clk/imx/Makefile                      |   2 +-
>  drivers/clk/imx/clk-imx51-imx53.c             | 549 ++++++++++++++++++
>  6 files changed, 657 insertions(+), 1 deletion(-)
>  create mode 100644 drivers/clk/imx/clk-imx51-imx53.c
> 
> -- 
> 2.17.1
> 
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
> 

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2018-08-27  7:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-25 21:03 Andrey Smirnov
2018-08-25 21:03 ` [PATCH 1/6] clk: i.MX: Port Linux clock tree for i.MX51 and i.MX53 Andrey Smirnov
2018-08-27  7:46   ` Sascha Hauer
2018-08-27 23:22     ` Andrey Smirnov
2018-08-25 21:03 ` [PATCH 2/6] ARM: imx51-zii-rdu1: Swtich to using Linux clock tree Andrey Smirnov
2018-08-27  9:15   ` Roland Hieber
2018-08-25 21:03 ` [PATCH 3/6] ARM: freescale-mx51-babbage: " Andrey Smirnov
2018-08-25 21:03 ` [PATCH 4/6] ARM: freescale-mx51-babbage: Add USBH1 PHY reset sequence Andrey Smirnov
2018-08-25 21:03 ` [PATCH 5/6] dts: imx51-babbage: Add USBH1 iomux configuration Andrey Smirnov
2018-08-25 21:03 ` [PATCH 6/6] ARM: imx51-zii-rdu1: Add USBH1,2 " Andrey Smirnov
2018-08-27  7:49 ` Sascha Hauer [this message]
2018-08-29  3:03   ` [PATCH 0/6] i.MX51 RDU1 and Babbage USB fixes Andrey Smirnov
2018-08-29  7:41     ` Sascha Hauer

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=20180827074939.wx7vzos7qg7o23hb@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=andrew.smirnov@gmail.com \
    --cc=barebox@lists.infradead.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