From: David Miller <davem@davemloft.net>
To: robert.jarzmik@free.fr
Cc: robh+dt@kernel.org, mark.rutland@arm.com, daniel@zonque.org,
haojian.zhuang@gmail.com, jic23@cam.ac.uk, dhowells@redhat.com,
nico@fluxnic.net, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-am33-list@redhat.com
Subject: Re: [PATCH v3 0/4] support smc91x on mainstone and devicetree
Date: Tue, 18 Oct 2016 14:14:37 -0400 (EDT) [thread overview]
Message-ID: <20161018.141437.2029098820682032692.davem@davemloft.net> (raw)
In-Reply-To: <1476733532-29716-1-git-send-email-robert.jarzmik@free.fr>
From: Robert Jarzmik <robert.jarzmik@free.fr>
Date: Mon, 17 Oct 2016 21:45:28 +0200
> This serie aims at bringing support to mainstone board on a device-tree based
> build, as what is already in place for legacy mainstone.
>
> The bulk of the mainstone "specific" behavior is that a u16 write doesn't work
> on a address of the form 4*n + 2, while it works on 4*n.
>
> The legacy workaround was in SMC_outw(), with calls to
> machine_is_mainstone(). These calls don't work with a pxa27x-dt machine type,
> which is used when a generic device-tree pxa27x machine is used to boot the
> mainstone board.
>
> Therefore, this serie enables the smc91c111 adapter of the mainstone board to
> work on a device-tree build, exaclty as it's been working for years with the
> legacy arch/arm/mach-pxa/mainstone.c definition.
>
> As a sum up, this extends an existing mechanism to device-tree based pxa platforms.
Series applied, thanks.
prev parent reply other threads:[~2016-10-18 18:14 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
[not found] ` <1476733532-29716-1-git-send-email-robert.jarzmik-GANU6spQydw@public.gmane.org>
2016-10-17 19:45 ` [PATCH v3 3/4] net: smc91x: take into account half-word workaround Robert Jarzmik
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 ` David Miller [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=20161018.141437.2029098820682032692.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=daniel@zonque.org \
--cc=devicetree@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=haojian.zhuang@gmail.com \
--cc=jic23@cam.ac.uk \
--cc=linux-am33-list@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=robert.jarzmik@free.fr \
--cc=robh+dt@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).