mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Michael Grzeschik <mgr@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2 3/3] ARM: i.MX6: add Technexion Pico Hobbit support
Date: Tue, 6 Jun 2017 13:03:48 +0200	[thread overview]
Message-ID: <20170606110348.qogfyllbixa5wfaf@pengutronix.de> (raw)
In-Reply-To: <20170606061840.3ygatsyaswtpqebz@pengutronix.de>

On Tue, Jun 06, 2017 at 08:18:40AM +0200, Sascha Hauer wrote:
> On Fri, Jun 02, 2017 at 03:18:08PM +0200, Michael Grzeschik wrote:
> > This adds support support for the i.MX6UL Technexion Pico Hobbit.
> > The board comes with different amounts of RAM. We create one image
> > for the 256MB and one for the 512MB variant.
> > 
> > Signed-off-by: Michael Grzeschik <m.grzeschik@pengutronix.de>
> > ---
> > v1 -> v2: - removed already prepared clock setup
> > 
> > +
> > +&usdhc1 {
> > +	#address-cells = <1>;
> > +	#size-cells = <1>;
> > +
> > +	partition@0 {
> > +		label = "barebox";
> > +		reg = <0x0 0xc0000>;
> > +	};
> > +
> > +	environment_usdhc1: partition@c0000 {
> > +		label = "barebox-environment";
> > +		reg = <0xc0000 0x40000>;
> > +	};
> > +};
> > +
> > +&fec2 {
> > +	/*
> > +	  There are two possible ways to start the phy. Let the hardware
> > +	  reset it properly or reset it a second time in software.
> > +	  Unfortunetly the phy needs some microseconds after reset to
> > +	  settle down. As there is no property like
> > +	  phy-post-reset-delay, we better leave the reset to the
> > +	  hardware.
> > +	*/
> > +	/delete-property/ phy-reset-gpios;
> > +	/delete-property/ phy-reset-duration;
> 
> Recent Kernels support phy-reset-post-delay. Can we just add support for
> it in barebox aswell?

Could we for now stick with this? When I write the phy-reset-post-delay
patches I will then adopt this node in the regarding series. This gives
me some time, as I can not test the post-delay patch in the next two
weeks.

Thanks,
Michael

-- 
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

  reply	other threads:[~2017-06-06 11:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02 13:18 [PATCH v2 0/3] imx6ul: " Michael Grzeschik
2017-06-02 13:18 ` [PATCH v2 1/3] ARM: i.MX: setup ENET_TX_CLK_DIR in imx6_init for every imx6ul Michael Grzeschik
2017-06-02 13:18 ` [PATCH v2 2/3] ARM: phytec-som-imx6: remove needles enet refclk setup Michael Grzeschik
2017-06-02 13:18 ` [PATCH v2 3/3] ARM: i.MX6: add Technexion Pico Hobbit support Michael Grzeschik
2017-06-06  6:18   ` Sascha Hauer
2017-06-06 11:03     ` Michael Grzeschik [this message]
2017-06-07  7:40       ` 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=20170606110348.qogfyllbixa5wfaf@pengutronix.de \
    --to=mgr@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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