linux-kernel - Re: [PATCH 10/32] ARM: dts: omap3-gta04: update gpmc NAND setup

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 25 Jul 2018 10:10:59 +0200
From:   Ladislav Michl <ladis@...ux-mips.org>
To:     "H. Nikolaus Schaller" <hns@...delico.com>
Cc:     Marek Belisko <marek@...delico.com>,
        Benoît Cousson <bcousson@...libre.com>,
        Tony Lindgren <tony@...mide.com>,
        Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        linux-omap@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, letux-kernel@...nphoenux.org
Subject: Re: [PATCH 10/32] ARM: dts: omap3-gta04: update gpmc NAND setup

On Wed, Jul 25, 2018 at 08:58:42AM +0200, H. Nikolaus Schaller wrote:
> to better match omap3-beagle.dts (which was the basis
> of designing the GTA04).
> 
> Signed-off-by: H. Nikolaus Schaller <hns@...delico.com>
> ---
>  arch/arm/boot/dts/omap3-gta04.dtsi | 14 +++++++-------
>  1 file changed, 7 insertions(+), 7 deletions(-)
> 
> diff --git a/arch/arm/boot/dts/omap3-gta04.dtsi b/arch/arm/boot/dts/omap3-gta04.dtsi
> index 03fe404cbf56..9568e0c4d4bf 100644
> --- a/arch/arm/boot/dts/omap3-gta04.dtsi
> +++ b/arch/arm/boot/dts/omap3-gta04.dtsi
> @@ -616,27 +616,27 @@
>  		interrupt-parent = <&gpmc>;
>  		interrupts = <0 IRQ_TYPE_NONE>, /* fifoevent */
>  			     <1 IRQ_TYPE_NONE>;	/* termcount */
> +		ti,nand-ecc-opt = "ham1";
> +		rb-gpios = <&gpmc 0 GPIO_ACTIVE_HIGH>; /* gpmc_wait0 */
>  		nand-bus-width = <16>;
> -		ti,nand-ecc-opt = "bch8";

You are using weeker ECC scheme just to be compatible with another machine?
So now you cannot boot already deployed filesystem... Also is it enough for
NAND chip used?

	ladis

> +		#address-cells = <1>;
> +		#size-cells = <1>;
>  
> -		gpmc,sync-clk-ps = <0>;
> +		gpmc,device-width = <2>;
>  		gpmc,cs-on-ns = <0>;
>  		gpmc,cs-rd-off-ns = <44>;
>  		gpmc,cs-wr-off-ns = <44>;
>  		gpmc,adv-on-ns = <6>;
>  		gpmc,adv-rd-off-ns = <34>;
>  		gpmc,adv-wr-off-ns = <44>;
> -		gpmc,we-off-ns = <40>;
>  		gpmc,oe-off-ns = <54>;
> +		gpmc,we-off-ns = <40>;
>  		gpmc,access-ns = <64>;
>  		gpmc,rd-cycle-ns = <82>;
>  		gpmc,wr-cycle-ns = <82>;
>  		gpmc,wr-access-ns = <40>;
>  		gpmc,wr-data-mux-bus-ns = <0>;
> -		gpmc,device-width = <2>;
> -
> -		#address-cells = <1>;
> -		#size-cells = <1>;
> +		gpmc,sync-clk-ps = <0>;
>  
>  		x-loader@0 {
>  			label = "X-Loader";
> -- 
> 2.12.2
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html