From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms@verge.net.au>
Cc: netdev@vger.kernel.org, nobuhiro.iwamatsu.yj@renesas.com,
linux-sh@vger.kernel.org, phil.edworthy@renesas.com
Subject: Re: [PATCH 2/2] sh_eth: add R-Car support for real
Date: Mon, 08 Apr 2013 13:45:14 +0000 [thread overview]
Message-ID: <5162C9EA.6060005@cogentembedded.com> (raw)
In-Reply-To: <20130408090451.GC8917@verge.net.au>
Hello.
On 08-04-2013 13:04, Simon Horman wrote:
>>> Commit d0418bb7123f44b23d69ac349eec7daf9103472f (net: sh_eth: Add eth support
>>> for R8A7779 device) was a failed attempt to add support for one of members of
>>> the R-Car SoC family. That's for three reasons: it treated R8A7779 the same
>>> as SH7724 except including quite dirty hack adding ECMR_ELB bit to the mask
>>> in sh_eth_set_rate() while not removing ECMR_RTM bit (despite it's reserved in
>>> R-Car Ether), and it didn't add a new register offset array despite the closest
>>> SH_ETH_REG_FAST_SH4 mapping differs by 0x200 to the offsets all the R-Car Ether
>>> registers have, and also some of the registers in this old mapping don't exist
>>> on R-Car Ether (due to this, SH7724's 'sh_eth_my_cpu_data' structure is not
>>> adequeate for R-Car too). Fix all these shortcomings, restoring the SH7724
>>> related section to its pristine state...
>>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>> Hi Sergei,
>> thanks for this and sorry for not noticing it earlier.
>> I will try exercising it on the r8a7790 lager.
> I am having a little trouble getting bringing up a link on the
> r8a7790 lager. I wonder if:
> * You know of any sh_eth side changes that need to be made,
> other than adding r8a7790 obvious ones relating to adding
> ARCH_R8A7790 wherever ARCH_R8A7779 is found.
Unfortunately, the only datasheet for R8A7790 Ether I have is in Japanese.
And I don't have the board info either. :-(
> * You have any sample board code for the marzen/r8a7779 or
> bockw/r8a7778 handy.
On Marzen the driver simply doesn't work right (and I don't even have the
datasheet for the Ethernet daughter board that I have, only for some other
type of board), on the BOCK-W the driver works but I have only tested it with
the version 1 of Morimoto-san's R8A7778/BOCK-W patches (which included pinmux
support), so this patch doesn't compile anymore with the current
renesas.git/next. With BOCK-W you need to set 'no_ether_link' in the platform
data since the Ether's LINK signal is connected to PHY's link/activity LED output.
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms@verge.net.au>
Cc: netdev@vger.kernel.org, nobuhiro.iwamatsu.yj@renesas.com,
linux-sh@vger.kernel.org, phil.edworthy@renesas.com
Subject: Re: [PATCH 2/2] sh_eth: add R-Car support for real
Date: Mon, 08 Apr 2013 17:45:14 +0400 [thread overview]
Message-ID: <5162C9EA.6060005@cogentembedded.com> (raw)
In-Reply-To: <20130408090451.GC8917@verge.net.au>
Hello.
On 08-04-2013 13:04, Simon Horman wrote:
>>> Commit d0418bb7123f44b23d69ac349eec7daf9103472f (net: sh_eth: Add eth support
>>> for R8A7779 device) was a failed attempt to add support for one of members of
>>> the R-Car SoC family. That's for three reasons: it treated R8A7779 the same
>>> as SH7724 except including quite dirty hack adding ECMR_ELB bit to the mask
>>> in sh_eth_set_rate() while not removing ECMR_RTM bit (despite it's reserved in
>>> R-Car Ether), and it didn't add a new register offset array despite the closest
>>> SH_ETH_REG_FAST_SH4 mapping differs by 0x200 to the offsets all the R-Car Ether
>>> registers have, and also some of the registers in this old mapping don't exist
>>> on R-Car Ether (due to this, SH7724's 'sh_eth_my_cpu_data' structure is not
>>> adequeate for R-Car too). Fix all these shortcomings, restoring the SH7724
>>> related section to its pristine state...
>>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>> Hi Sergei,
>> thanks for this and sorry for not noticing it earlier.
>> I will try exercising it on the r8a7790 lager.
> I am having a little trouble getting bringing up a link on the
> r8a7790 lager. I wonder if:
> * You know of any sh_eth side changes that need to be made,
> other than adding r8a7790 obvious ones relating to adding
> ARCH_R8A7790 wherever ARCH_R8A7779 is found.
Unfortunately, the only datasheet for R8A7790 Ether I have is in Japanese.
And I don't have the board info either. :-(
> * You have any sample board code for the marzen/r8a7779 or
> bockw/r8a7778 handy.
On Marzen the driver simply doesn't work right (and I don't even have the
datasheet for the Ethernet daughter board that I have, only for some other
type of board), on the BOCK-W the driver works but I have only tested it with
the version 1 of Morimoto-san's R8A7778/BOCK-W patches (which included pinmux
support), so this patch doesn't compile anymore with the current
renesas.git/next. With BOCK-W you need to set 'no_ether_link' in the platform
data since the Ether's LINK signal is connected to PHY's link/activity LED output.
WBR, Sergei
next prev parent reply other threads:[~2013-04-08 13:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 20:50 [PATCH 2/2] sh_eth: add R-Car support for real Sergei Shtylyov
2013-03-28 21:51 ` Sergei Shtylyov
2013-03-29 19:31 ` David Miller
2013-03-29 19:31 ` David Miller
2013-04-08 2:39 ` Simon Horman
2013-04-08 2:39 ` Simon Horman
2013-04-08 9:04 ` Simon Horman
2013-04-08 9:04 ` Simon Horman
2013-04-08 13:45 ` Sergei Shtylyov [this message]
2013-04-08 13:45 ` Sergei Shtylyov
2013-04-08 14:40 ` phil.edworthy
2013-04-08 14:40 ` phil.edworthy
2013-04-09 13:08 ` Sergei Shtylyov
2013-04-09 13:08 ` Sergei Shtylyov
2013-04-08 13:34 ` Sergei Shtylyov
2013-04-08 13:34 ` Sergei Shtylyov
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=5162C9EA.6060005@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=horms@verge.net.au \
--cc=linux-sh@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nobuhiro.iwamatsu.yj@renesas.com \
--cc=phil.edworthy@renesas.com \
/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.