netdev - MPC885 spi: fsl-spi and SCC2 : Allow dynamic allocation of CPM1 pRAM

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>] [day] [month] [year] [list]

Message-ID: <9C239FD147603C458A197774921522B132937FE4@ikhexmbxc02n01.ikhex.ikoula.com>
Date:	Wed, 6 May 2015 23:18:40 +0000
From:	Sebastien BLAVIER <sebastien.blavier@...ianesysteme.com>
To:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: MPC885 spi: fsl-spi and SCC2 : Allow dynamic allocation of CPM1 pRAM


Dear,


I would like to know if a patch of file spi_mpc8xxx.c exists to use SPI and SCC2 on MPC885 for linux 2.6.35?


The start of driver fails  => the function mpc8xxx_spi_cpm_get_pram is KO due to :  spi_base_ofs = cpm_muram_alloc_fixed(iprop[2], 2);  => spi_base_ofs invalid .


if i do this change spi_base_ofs = iprop[2], 2; in function mpc8xxx_spi_cpm_get_pram, the driver is loaded but the SCC2 does not work any more and SPI does not work too.


Arch setup : 
{CPM_PORTB, 28, CPM_PIN_OUTPUT},

{CPM_PORTB, 29, CPM_PIN_OUTPUT},

{CPM_PORTB, 30, CPM_PIN_OUTPUT},



My DTS below :
          cpm@9c0 {
              #address-cells = <1>;
              #size-cells = <1>;
              compatible = "fsl,mpc885-cpm", "fsl,cpm1";
....
              spi: spi@aa0 {
                  #address-cells = <1>;
                  #size-cells = <0>;
                  cell-index = <0>;
                  compatible = "fsl,spi", "fsl,cpm1-spi";
                  reg = <0xaa0 0x12 0x3d80 0x30>;
		  interrupts = <5>;


Sébastien Blavier.--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html