From: Matthew Hagan <mnhagan88@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
Russell King <linux@armlinux.org.uk>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] ARM: dts: NSP: Correct amac_base lengths, mailbox reg and add amac3
Date: Tue, 16 Jun 2020 21:19:54 +0100 [thread overview]
Message-ID: <acbf9159-375c-5dcc-3353-e9d60496516e@gmail.com> (raw)
In-Reply-To: <c08a06a8-de71-d1cd-541d-2e15a23f130a@gmail.com>
On 14/06/2020 23:28, Florian Fainelli wrote:
>
>
> On 6/9/2020 9:58 AM, Matthew Hagan wrote:
>> According to gmac/src/et/sys/et_linux.c, IORESOURCE_MEM end address for each
>> mac is IPROC_GMACx_REG_BASE+0xbff.
>
> The datasheet shows an entire GMAC to end at 0x1000 from its base offset
> which is likely what was used to construct this DTS, I do not believe
> this is a functional change, and if we look at the register details, the
> last register starts at 0xb44 so 0xc00 is giving a little bit of
> headroom. In practice it does not change anything since you are still
> going to need a full 4KB page frame to map the registers.
>
>>
>> The FA2 mailbox is specified at 0x18025000 but should actually be 0x18025c00,
>> length 0x400 according to socregs_nsp.h and board_bu.c. amac3 is at 25000.
>
> Yes, FA2 definitively start 0x18025c00, and ends 0x400 later, so I did
> split this patch in three patches:
>
> - one that fixes the FA2 base address, which can be queued to stable
> kernel branches
> - one that changes the AMAC register size
> - one that adds the AMAC3
Since AMAC3 has been added with interrupt 150, should the mailbox
interrupt not also be incremented to 151?
>
> Such that the first patch can be queued for -stable fixes, whereas the
> other two, not being functional changes are candidates for devicetree/next.
>
> Result here:
>
> https://github.com/Broadcom/stblinux/commits/devicetree/next
>
> Thanks!
>
Thanks,
Matthew
next prev parent reply other threads:[~2020-06-16 20:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 16:58 [PATCH 1/3] ARM: dts: NSP: Disable PL330 by default, add dma-coherent property Matthew Hagan
2020-06-09 16:58 ` [PATCH 2/3] ARM: dts: NSP: Correct amac_base lengths, mailbox reg and add amac3 Matthew Hagan
2020-06-14 22:28 ` Florian Fainelli
2020-06-16 20:19 ` Matthew Hagan [this message]
2020-06-17 21:54 ` Florian Fainelli
2020-06-09 16:58 ` [PATCH 3/3] ARM: bcm: Select ARM_TIMER_SP804 for ARCH_BCM_NSP Matthew Hagan
2020-06-14 22:15 ` Florian Fainelli
2020-06-14 22:17 ` [PATCH 1/3] ARM: dts: NSP: Disable PL330 by default, add dma-coherent property Florian Fainelli
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=acbf9159-375c-5dcc-3353-e9d60496516e@gmail.com \
--to=mnhagan88@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.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 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).