[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6214e145-b408-70f1-bc6f-db066cbe94b1@schinagl.nl>
Date: Fri, 15 Jul 2016 10:57:18 +0200
From: Olliver Schinagl <oliver@...inagl.nl>
To: stefan.mavrodiev@...il.com,
linux-sunxi <linux-sunxi@...glegroups.com>
Cc: christo.radev@...il.com, radoslav.kolev@...edlynx.com,
wens@...e.org, maxime.ripard@...e-electrons.com,
tsvetan@...mex.com, robh+dt@...nel.org, pawel.moll@....com,
mark.rutland@....com, ijc+devicetree@...lion.org.uk,
galak@...eaurora.org, linux@....linux.org.uk, hdegoede@...hat.com,
dev@...ux-sunxi.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] ARM: dts: sunxi: Add a olinuxino-lime2-emmc
On 15-07-16 10:39, stefan.mavrodiev@...il.com wrote:
> Hi Olliver,
>
> Why are you using nRST signal?
> What I mean is this pin is inactive on this eMMC chip. To use the signal
> byte 162 of ECSD registers should be written.
Then that sounds like a bug in the mmc layer I would say (or a missing
attribute in the dts), we have a nRST signal it is wired, if the chip
ignores it, then nothing lost, if the chip needs to be initialized with
byte 162 of the ECSD register to make the nRST work, then that it sounds
like it should be fixed there?
By ommitting the nRST signal just because the chip isn't properly
initialized sounds more like a work-around to me, but I could be wrong
and see things wrong.
What do the mmc guys, who have far more experience here, say?
>
> On my board, this "reset" signal causes eMMC not to work.
That supprises me, as afaik I was using it just fine...
Olliver
>
> Best regards,
> Stefan Mavrodiev
Powered by blists - more mailing lists