From: Eugeniy.Paltsev@synopsys.com (Eugeniy Paltsev)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH v3] ARC: [plat-hsdk]: Add reset controller node to manage ethernet reset
Date: Thu, 5 Oct 2017 13:26:25 +0000 [thread overview]
Message-ID: <1507209984.3461.13.camel@synopsys.com> (raw)
In-Reply-To: <64d3fb1d-8d6e-3c5f-f143-c3e6a205a95b@synopsys.com>
On Thu, 2017-10-05@06:04 -0700, Vineet Gupta wrote:
> Hi Eugeniy,
>
> On 09/22/2017 09:49 AM, Eugeniy Paltsev wrote:
> > DW ethernet controller on HSDK hangs sometimes after SW reset, so
> > add reset node to make possible to reset DW ethernet controller HW.
> >
> > Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev at synopsys.com>
> > ---
> > Changes v2 -> v3:
> > ???* Remove v1 suffix as we finaly got rid of v1 suffix in reset
> > ?????driver and docs.
> > ???* Rename reset node to "reset-controller" for consistency with
> > ?????the other bindings.
> >
> > Changes v1 -> v2:
> > ???* Enable HSDK reset driver in hsdk_defconfig
>
> Revisiting this given that changes to driver have been merged upstream: we?
> currently carry a reset workaround for axs+ethernet, i.e. your patch
>
> ?????ARC: [plat-axs103] Add temporary quirk to reset ethernet IP
>
> But there's nothing similar for HSDK. IOW, we don't need to revert anything foro?
> hsdk, after this gets applied ?
That?s correct. We don't need to revert anything for hsdk.
We only need to apply this patch.
> -Vineet
--
?Eugeniy Paltsev
WARNING: multiple messages have this Message-ID (diff)
From: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
To: "Eugeniy.Paltsev@synopsys.com" <Eugeniy.Paltsev@synopsys.com>,
Vineet Gupta <Vineet.Gupta1@synopsys.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Alexey.Brodkin@synopsys.com" <Alexey.Brodkin@synopsys.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v3] ARC: [plat-hsdk]: Add reset controller node to manage ethernet reset
Date: Thu, 5 Oct 2017 13:26:25 +0000 [thread overview]
Message-ID: <1507209984.3461.13.camel@synopsys.com> (raw)
In-Reply-To: <64d3fb1d-8d6e-3c5f-f143-c3e6a205a95b@synopsys.com>
On Thu, 2017-10-05 at 06:04 -0700, Vineet Gupta wrote:
> Hi Eugeniy,
>
> On 09/22/2017 09:49 AM, Eugeniy Paltsev wrote:
> > DW ethernet controller on HSDK hangs sometimes after SW reset, so
> > add reset node to make possible to reset DW ethernet controller HW.
> >
> > Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
> > ---
> > Changes v2 -> v3:
> > * Remove v1 suffix as we finaly got rid of v1 suffix in reset
> > driver and docs.
> > * Rename reset node to "reset-controller" for consistency with
> > the other bindings.
> >
> > Changes v1 -> v2:
> > * Enable HSDK reset driver in hsdk_defconfig
>
> Revisiting this given that changes to driver have been merged upstream: we
> currently carry a reset workaround for axs+ethernet, i.e. your patch
>
> ARC: [plat-axs103] Add temporary quirk to reset ethernet IP
>
> But there's nothing similar for HSDK. IOW, we don't need to revert anything foro
> hsdk, after this gets applied ?
That’s correct. We don't need to revert anything for hsdk.
We only need to apply this patch.
> -Vineet
--
Eugeniy Paltsev
next prev parent reply other threads:[~2017-10-05 13:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 16:49 [PATCH v3] ARC: [plat-hsdk]: Add reset controller node to manage ethernet reset Eugeniy Paltsev
2017-09-22 16:49 ` Eugeniy Paltsev
2017-09-27 17:40 ` Vineet Gupta
2017-09-27 17:40 ` Vineet Gupta
2017-09-27 18:55 ` Eugeniy Paltsev
2017-09-27 18:55 ` Eugeniy Paltsev
2017-09-27 18:55 ` Eugeniy Paltsev
2017-10-05 13:04 ` Vineet Gupta
2017-10-05 13:04 ` Vineet Gupta
2017-10-05 13:04 ` Vineet Gupta
2017-10-05 13:26 ` Eugeniy Paltsev [this message]
2017-10-05 13:26 ` Eugeniy Paltsev
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=1507209984.3461.13.camel@synopsys.com \
--to=eugeniy.paltsev@synopsys.com \
--cc=linux-snps-arc@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 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.