All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
To: Grygorii Strashko <grygorii.strashko-l0cyMroinI0@public.gmane.org>
Cc: Sekhar Nori <nsekhar-l0cyMroinI0@public.gmane.org>,
	Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v2 0/3] ARM: dts: omap: workarounds for Ethernet PHY strap on DRA71 and DRA72 EVMs
Date: Thu, 10 Aug 2017 10:37:19 -0700	[thread overview]
Message-ID: <20170810173718.GP8569@atomide.com> (raw)
In-Reply-To: <ca0d0615-d813-d00b-e853-25df9a5c49b6-l0cyMroinI0@public.gmane.org>

* Grygorii Strashko <grygorii.strashko-l0cyMroinI0@public.gmane.org> [170809 15:27]:
> On 08/09/2017 09:02 AM, Sekhar Nori wrote:
> > Here are some patches to overcome incorrect Ethernet PHY strap settings
> > on DRA72x EVM Rev C and DRA71 EVM. Both of these boards use TI's DP83867
> > PHY.
> > 
> > The incorrect PHY strap settings cause a voilation of PHY specification
> > and need to be worked around in software as documented in the commit
> > messages. But there is no known issue that these patches fix.
...

> Reviewed-by: Grygorii Strashko <grygorii.strashko-l0cyMroinI0@public.gmane.org>

Applying dts changes into omap-for-v4.14/fixes-not-urgent
and defconfig into omap-for-v4.14/defconfig.

Thanks,

Tony
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] ARM: dts: omap: workarounds for Ethernet PHY strap on DRA71 and DRA72 EVMs
Date: Thu, 10 Aug 2017 10:37:19 -0700	[thread overview]
Message-ID: <20170810173718.GP8569@atomide.com> (raw)
In-Reply-To: <ca0d0615-d813-d00b-e853-25df9a5c49b6@ti.com>

* Grygorii Strashko <grygorii.strashko@ti.com> [170809 15:27]:
> On 08/09/2017 09:02 AM, Sekhar Nori wrote:
> > Here are some patches to overcome incorrect Ethernet PHY strap settings
> > on DRA72x EVM Rev C and DRA71 EVM. Both of these boards use TI's DP83867
> > PHY.
> > 
> > The incorrect PHY strap settings cause a voilation of PHY specification
> > and need to be worked around in software as documented in the commit
> > messages. But there is no known issue that these patches fix.
...

> Reviewed-by: Grygorii Strashko <grygorii.strashko@ti.com>

Applying dts changes into omap-for-v4.14/fixes-not-urgent
and defconfig into omap-for-v4.14/defconfig.

Thanks,

Tony

  parent reply	other threads:[~2017-08-10 17:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-09 14:02 [PATCH v2 0/3] ARM: dts: omap: workarounds for Ethernet PHY strap on DRA71 and DRA72 EVMs Sekhar Nori
2017-08-09 14:02 ` Sekhar Nori
2017-08-09 14:02 ` [PATCH v2 1/3] ARM: dts: dra71-evm: workaround incorrect DP83867 RX_CTRL pin strap Sekhar Nori
2017-08-09 14:02   ` Sekhar Nori
     [not found] ` <cover.1502284400.git.nsekhar-l0cyMroinI0@public.gmane.org>
2017-08-09 14:02   ` [PATCH v2 2/3] ARM: dts: dra72-evm-revc: " Sekhar Nori
2017-08-09 14:02     ` Sekhar Nori
2017-08-09 14:02   ` [PATCH v2 3/3] ARM: omap2plus_defconfig: enable DP83867 phy driver Sekhar Nori
2017-08-09 14:02     ` Sekhar Nori
2017-08-09 22:26   ` [PATCH v2 0/3] ARM: dts: omap: workarounds for Ethernet PHY strap on DRA71 and DRA72 EVMs Grygorii Strashko
2017-08-09 22:26     ` Grygorii Strashko
     [not found]     ` <ca0d0615-d813-d00b-e853-25df9a5c49b6-l0cyMroinI0@public.gmane.org>
2017-08-10 17:37       ` Tony Lindgren [this message]
2017-08-10 17:37         ` Tony Lindgren

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=20170810173718.GP8569@atomide.com \
    --to=tony-4v6ys6ai5vpbdgjk7y7tuq@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=grygorii.strashko-l0cyMroinI0@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
    --cc=nsekhar-l0cyMroinI0@public.gmane.org \
    --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.