From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Andrew <andrew@ncrmnt.org>,
Gregory CLEMENT <gregory.clement@free-electrons.com>
Cc: Andrew Lunn <andrew@lunn.ch>, Rob Herring <robh+dt@kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>,
Linus Walleij <linus.walleij@linaro.org>,
Wolfram Sang <wsa@the-dreams.de>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Jason Cooper <jason@lakedaemon.net>
Subject: Re: Fwd: Re: [PATCH 2/2] ARM: mvebu: dts: Add dts file for DLink DNS-327L
Date: Sun, 03 May 2015 12:58:53 +0200 [thread overview]
Message-ID: <5545FF6D.9040205@gmail.com> (raw)
In-Reply-To: <4e7e91562aac6a260885bf2d12174060@mail.ncrmnt.org>
On 03.05.2015 12:18, Andrew wrote:
[...]
> Sorry for the long delay with testing, but here come the results.
> I've rebased everything to 4.1-rc1
>
> 1. WFI + DeepIdle => freeze after approx:
> * 1 hours and 30 minutes, first test
> * 3 hours and 40 minutes, second test
> 2. WFI only (DeepIdle disabled via sysfs) => Still alive after 13 hours
> and counting
>
> The proper patchset will follow as soon as I figure out what change broke
> dns320l-daemon (The utility that speaks to weltrend mcu on ttyS1)
> It was working on 3.18.6, on 3.19 and up - it writes data to the port
> (and mcu acks it),
> but can't read any responses.
>
> Same thing happens to the python (pyserial inside) implementation of the
> fan-daemon:
> https://github.com/martignlo/DNS-320L
Andrew,
did you realize that you request a non-standard UART baudrate in your
python code above:
port = serial.Serial("/dev/ttyS1", 115600, 8, "N", 1, 0.1)
s/115600/115200/
Does that fix your communication issues?
Sebastian
next prev parent reply other threads:[~2015-05-03 10:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-12 11:43 Fwd: Re: [PATCH 2/2] ARM: mvebu: dts: Add dts file for DLink DNS-327L Andrew
2015-04-12 12:16 ` Sebastian Hesselbarth
2015-04-12 13:02 ` Andrew
2015-04-12 14:58 ` Andrew Lunn
[not found] ` <20150412145857.GA14038-g2DYL2Zd6BY@public.gmane.org>
2015-04-12 15:41 ` Andrew
[not found] ` <b172d775afa24cea69a9490f531c6b37-IcawJbj+vY1vZ+LtbKW8tg@public.gmane.org>
2015-04-12 19:47 ` Andrew Lunn
2015-04-13 14:16 ` Gregory CLEMENT
2015-04-13 14:32 ` Andrew
[not found] ` <1ec8906f00468ca5a9fa227f8c83fe69-IcawJbj+vY1vZ+LtbKW8tg@public.gmane.org>
2015-04-20 15:04 ` Gregory CLEMENT
2015-04-20 15:15 ` Andrew
2015-04-20 15:17 ` Gregory CLEMENT
2015-05-03 10:18 ` Andrew
2015-05-03 10:58 ` Sebastian Hesselbarth [this message]
2015-05-03 11:37 ` Andrew
2015-05-06 12:13 ` Gregory CLEMENT
2015-05-06 13:39 ` Andrew
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=5545FF6D.9040205@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=andrew@lunn.ch \
--cc=andrew@ncrmnt.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregory.clement@free-electrons.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jason@lakedaemon.net \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=wsa@the-dreams.de \
/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).