devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: grygorii <grygorii.strashko@ti.com>
Cc: linux-omap@vger.kernel.org,
	"Benoît Cousson" <bcousson@baylibre.com>,
	devicetree@vger.kernel.org,
	"Ivan Khoronzhuk" <ivan.khoronzhuk@linaro.org>,
	Keerthy <j-keerthy@ti.com>
Subject: Re: [PATCH 0/3] Drop platform data for cpsw for am3/4 and dra7
Date: Mon, 26 Aug 2019 08:19:08 -0700	[thread overview]
Message-ID: <20190826151908.GU52127@atomide.com> (raw)
In-Reply-To: <a4467e6c-88f3-eac8-322a-c0e40360ba36@ti.com>

* grygorii <grygorii.strashko@ti.com> [190815 16:44]:
> Hi Tony,
> 
> On 14/08/2019 13:19, Tony Lindgren wrote:
> > Hi all,
> > 
> > Here are changes to drop legacy platform data for cpsw for am3, am4
> > and dra7. Please review and test, I was not able to boot my beagle
> > x15 as it seems to have a power supply problem and have only tested
> > on am3 and 4.
> 
> 
> Thank you.
> Reviewed-by: Grygorii Strashko <grygorii.strashko@ti.com>

Just to update the beagle x15 status, the issue I was seeing turned
out to be hung ftdi serial driver on my PC instead of a power supply
problem. Reloading USB modules fixed that.

Regards,

Tony

      reply	other threads:[~2019-08-26 15:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-14 10:19 [PATCH 0/3] Drop platform data for cpsw for am3/4 and dra7 Tony Lindgren
2019-08-14 10:19 ` [PATCH 1/3] ARM: dts: Add fck for cpsw mdio for omap variants Tony Lindgren
2019-08-14 10:19 ` [PATCH 2/3] ARM: OMAP2+: Drop legacy platform data for cpsw on am3 and am4 Tony Lindgren
2019-08-14 10:19 ` [PATCH 3/3] ARM: OMAP2+: Drop legacy platform data for cpsw on dra7 Tony Lindgren
2019-08-15 16:44 ` [PATCH 0/3] Drop platform data for cpsw for am3/4 and dra7 grygorii
2019-08-26 15:19   ` Tony Lindgren [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=20190826151908.GU52127@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=grygorii.strashko@ti.com \
    --cc=ivan.khoronzhuk@linaro.org \
    --cc=j-keerthy@ti.com \
    --cc=linux-omap@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).