From: Murali Karicheri <m-karicheri2@ti.com>
To: Santosh Shilimkar <santosh.shilimkar@oracle.com>,
ssantosh@kernel.org, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, linux@armlinux.org.uk,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] ARM: dts: keystone: remove bogus IO resource entry from PCI binding
Date: Thu, 2 Jun 2016 17:07:46 -0400 [thread overview]
Message-ID: <5750A022.2000601@ti.com> (raw)
In-Reply-To: <bdf18787-46ed-cc15-8914-fc14a3557681@oracle.com>
On 06/02/2016 02:08 PM, Santosh Shilimkar wrote:
> On 6/2/2016 8:17 AM, Murali Karicheri wrote:
>> The PCI DT bindings contain a bogus entry for IO space which is not
>> supported on Keystone. The current bogus entry has an invalid size
>> and throws following error during boot.
>>
>> [0.420713] keystone-pcie 21021000.pcie: error -22: failed to map
>> resource [io 0x0000-0x400000003fff]
>>
>> So remove it from the dts. While at it also add a bus-range
>> value that eliminates following log at boot up.
>>
>> [0.420659] No bus range found for /soc/pcie@21020000, using [bus 00-ff]
>>
>> Signed-off-by: Murali Karicheri <m-karicheri2@ti.com>
>> ---
> Both 1/2 and 2/2 looks fine to me. Will queue them for
> next merge window.
>
> Regards,
> Santosh
>
Ok. Thanks Santosh!
--
Murali Karicheri
Linux Kernel, Keystone
prev parent reply other threads:[~2016-06-02 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 15:17 [PATCH v1 1/2] ARM: dts: keystone: remove bogus IO resource entry from PCI binding Murali Karicheri
2016-06-02 15:17 ` [PATCH v1 2/2] ARM: dts: keystone: add interrupt property to PCI controller bindings Murali Karicheri
2016-06-02 18:08 ` [PATCH v1 1/2] ARM: dts: keystone: remove bogus IO resource entry from PCI binding Santosh Shilimkar
2016-06-02 21:07 ` Murali Karicheri [this message]
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=5750A022.2000601@ti.com \
--to=m-karicheri2@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=santosh.shilimkar@oracle.com \
--cc=ssantosh@kernel.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;
as well as URLs for NNTP newsgroup(s).