From: matthias.bgg@gmail.com (Matthias Brugger)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Mediatek: 32-bit DT update for v4.15
Date: Thu, 2 Nov 2017 12:47:05 +0100 [thread overview]
Message-ID: <e8fdd9a9-ce13-8804-aea0-46becc6f9730@gmail.com> (raw)
In-Reply-To: <1509423579.10793.10.camel@mtkswgap22>
Hi Arnd,
On 10/31/2017 05:19 AM, Ryder Lee wrote:
> Hi Arnd,
>
> We have 3 root ports in MT7623, but this is a bug in this chip where the
> HW designers wired the IRQs in a nonstandard way. We've tried to
> statically assign the bus portion of the address part in the parent
> interrupt-map before, but this approach cannot handle the case - if we
> attach the device in random order.
>
Ryder, please don't top post :)
> Thanks.
>
> On Mon, 2017-10-30 at 13:42 +0100, Arnd Bergmann wrote:
>> On Mon, Oct 23, 2017 at 12:06 AM, Matthias Brugger
>> <matthias.bgg@gmail.com> wrote:
>>>
>>> ----------------------------------------------------------------
>>> - mt76233 add PCIe node
>>
>> Could you clarify what the subnodes in the PCI node are for? It seems odd
>> to have "interrupt-map" properties in both the pcie controller and its child
>> nodes, and I want to ensure this is following the standard PCIe binding before
>> I pull it.
>>
Arnd, I didn't found the pull request in your next/dt branch.
Is there more clarification needed from our side?
Regards,
Matthias
next prev parent reply other threads:[~2017-11-02 11:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-22 22:06 [GIT PULL] Mediatek: 32-bit DT update for v4.15 Matthias Brugger
2017-10-30 12:42 ` Arnd Bergmann
2017-10-31 4:19 ` Ryder Lee
2017-11-02 11:47 ` Matthias Brugger [this message]
2017-11-02 16:05 ` Arnd Bergmann
2017-11-02 18:47 ` Matthias Brugger
2017-11-02 21:55 ` Arnd Bergmann
2017-11-03 1:37 ` Ryder Lee
2017-11-03 9:40 ` Arnd Bergmann
2017-11-03 11:52 ` Ryder Lee
2017-11-03 15:21 ` Arnd Bergmann
2017-11-05 1:41 ` Ryder Lee
2018-01-09 9:12 ` Ryder Lee
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=e8fdd9a9-ce13-8804-aea0-46becc6f9730@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=linux-arm-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox