Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/4] net: smc91x: take into account half-word workaround
Date: Mon, 17 Oct 2016 21:45:31 +0200	[thread overview]
Message-ID: <1476733532-29716-4-git-send-email-robert.jarzmik@free.fr> (raw)
In-Reply-To: <1476733532-29716-1-git-send-email-robert.jarzmik@free.fr>

For device-tree builds, platforms such as mainstone, idp and stargate2
must have their u16 writes all aligned on 32 bit boundaries. This is
already enabled in platform data builds, and this patch adds it to
device-tree builds.

Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr>
---
Since v1: rename dt property to pxa-u16-align4
---
 drivers/net/ethernet/smsc/smc91x.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/net/ethernet/smsc/smc91x.c b/drivers/net/ethernet/smsc/smc91x.c
index 705d99b2d947..65077c77082a 100644
--- a/drivers/net/ethernet/smsc/smc91x.c
+++ b/drivers/net/ethernet/smsc/smc91x.c
@@ -2326,6 +2326,8 @@ static int smc_drv_probe(struct platform_device *pdev)
 		if (!device_property_read_u32(&pdev->dev, "reg-shift",
 					      &val))
 			lp->io_shift = val;
+		lp->cfg.pxa_u16_align4 =
+			device_property_read_bool(&pdev->dev, "pxa-u16-align4");
 	}
 #endif
 
-- 
2.1.4

  parent reply	other threads:[~2016-10-17 19:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-17 19:45 [PATCH v3 0/4] support smc91x on mainstone and devicetree Robert Jarzmik
2016-10-17 19:45 ` [PATCH v3 1/4] ARM: pxa: enhance smc91x platform data Robert Jarzmik
2016-10-17 19:45 ` [PATCH v3 2/4] net: smc91x: isolate u16 writes alignment workaround Robert Jarzmik
2016-10-17 19:45 ` Robert Jarzmik [this message]
2016-10-17 19:45 ` [PATCH v3 4/4] net: smsc91x: add u16 workaround for pxa platforms Robert Jarzmik
2016-10-18 16:39   ` Rob Herring
2016-10-18 18:14 ` [PATCH v3 0/4] support smc91x on mainstone and devicetree David Miller

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=1476733532-29716-4-git-send-email-robert.jarzmik@free.fr \
    --to=robert.jarzmik@free.fr \
    --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