Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753364AbbBXV16 (ORCPT ); Tue, 24 Feb 2015 16:27:58 -0500 Received: from devils.ext.ti.com ([198.47.26.153]:32821 "EHLO devils.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753299AbbBXV1m (ORCPT ); Tue, 24 Feb 2015 16:27:42 -0500 From: Murali Karicheri To: , , , , , , , , , , , CC: Murali Karicheri Subject: [PATCH net-next 1/2] net: davinci_mdio: don't request io address range Date: Tue, 24 Feb 2015 16:27:30 -0500 Message-ID: <1424813251-31610-1-git-send-email-m-karicheri2@ti.com> X-Mailer: git-send-email 1.7.9.5 MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1540 Lines: 40 From: Grygorii Strashko Historically Davinci MDIO driver was created with assumption that MDIO is standalone device, but for Keystone 2 it's a part of NETCP module and now NETCP driver requests IO range which includes MDIO IO range too. This causes Keystone 2 networking stack failure during the boot. "netcp-1.0 2620110.netcp: Probe of module(netcp-gbe) failed with -16" Hence, don't request io address range from Davinci MDIO driver and just remap it. Signed-off-by: Grygorii Strashko Signed-off-by: Murali Karicheri --- drivers/net/ethernet/ti/davinci_mdio.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/ethernet/ti/davinci_mdio.c b/drivers/net/ethernet/ti/davinci_mdio.c index 98655b4..b13ec82 100644 --- a/drivers/net/ethernet/ti/davinci_mdio.c +++ b/drivers/net/ethernet/ti/davinci_mdio.c @@ -371,7 +371,7 @@ static int davinci_mdio_probe(struct platform_device *pdev) spin_lock_init(&data->lock); res = platform_get_resource(pdev, IORESOURCE_MEM, 0); - data->regs = devm_ioremap_resource(dev, res); + data->regs = devm_ioremap_nocache(dev, res->start, resource_size(res)); if (IS_ERR(data->regs)) { ret = PTR_ERR(data->regs); goto bail_out; -- 1.7.9.5 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/