From: Andrew <andrew@ncrmnt.org>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: 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,
Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@free-electrons.com>,
Jason Cooper <jason@lakedaemon.net>
Subject: Re: Fwd: Re: [PATCH 2/2] ARM: mvebu: dts: Add dts file for DLink DNS-327L
Date: Sun, 12 Apr 2015 16:02:12 +0300 [thread overview]
Message-ID: <cd7445f789f1082f464d464f77807f12@mail.ncrmnt.org> (raw)
In-Reply-To: <552A6209.9040903@gmail.com>
Sebastian Hesselbarth писал 12.04.2015 15:16:
> On 12.04.2015 13:43, Andrew wrote:
>> Sebastian Hesselbarth писал 12.04.2015 14:20:
>>> On 11.04.2015 22:29, Andrew Andrianov wrote:
>>>> Signed-off-by: Andrew Andrianov <andrew@ncrmnt.org>
> [...]
>>>> + * CONFIG_ARM_MVEBU_V7_CPUIDLE=y causes hard freezes every 1-8
>>>> hours
>>>
>>> I don't think the dts is the right place for Linux issues.
>>
>> Not sure if that's a hardware weirdness or software issue (yet).
>> Just checked - this goblin is there in 4.0-rc7.
>
> I understand the issue, but still the dts is not the right place
> for this comment.
Okay, got it.
I'll file a bug about this issue to the the bugzilla. However something
tells me it might not be cpuidle, but D-link. This one's sounds nasty
and it has been around since 3.16.x. How could it go unnoticed?
Unfortunately I have no other armada-370 hardware to test it.
>
> [...]
>>>> + marvell,nand-keep-config;
>>>> + marvell,nand-enable-arbiter;
>>>> + nand-on-flash-bbt;
>>>
>>> Do you know the ECC scheme used?
>>
>> Any hints on how to find it apart from dumping NAND controller
>> registers
>> from bootloader ?
>
> From the original bootlog:
>
> armada-nand armada-nand.0: Initialize HAL based NFC in 8bit mode with
> DMA Disabled using BCH 4bit ECC
>
> that translates into
>
> nand-ecc-strength = <4>;
> nand-ecc-step-size = <512>;
Thanks!
>
> [...]
>>>> + /* Hardwired into stock bootloader */
>>>
>>> I don't get the comment above.
>>
>> The stock u-boot is hacked with a 'failsafe' kernel address.
>
> Ok, the above partition isn't passed by the bootloader on mtdparts
> cmdline, i.e. that is why you call it "hardwired" ?
As far I got - stock u-boot knows nothing about partition tables and
operates just on raw NAND offsets.
> Just remove the comment, actually the whole partition table is
> "hacked" into the stock bootloader.
>
>> If for some reason running the 'bootcmd' fails, it reads
>> 5MiBs from partition @ (5d00000 + 0x800) and tries to boot it.
>> There's no way to change this via environment, only by replacing
>> the bootloader.
>> Personally I'm more happy with a simpler partition table, but I
>> guess upstream should be oriented towards the stock bootloader.
>
> Yeah, leave the original partition table. Any other, smarter
> bootloader can replace it.
>
> [...]
>> Thanks for the review, I'll resubmit the fixed patchset shortly.
>> Please disregard my [PATCH v2] messages. I've send them the moment
>> before
>> I noticed your email and review.
>
> Please always leave the Cc-list in place.
Sorry, I had to resend that email twice. First one to you, next to the
list
and others. I'm quite new to LKML so still playing with proper email
setup.
> And you should relax and leave patches there a day or two (or three).
> Not everybody is reading patches immediately.
>
> We are in no hurry, the current merge window is already closed,
> the new one is 6 weeks away.
>
> Sebastian
I only have a chance to play with the hardware at the weekend, since the
spare dns327l is at the country house, so I try to send fixes as soon as
get feedback while I can quickly test it.
--
Regards,
Andrew
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-04-12 13:02 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 [this message]
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
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=cd7445f789f1082f464d464f77807f12@mail.ncrmnt.org \
--to=andrew@ncrmnt.org \
--cc=andrew@lunn.ch \
--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=sebastian.hesselbarth@gmail.com \
--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).