[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <34890DB1679E41119ADB156E2CFEC4C9@subhasishg>
Date: Tue, 5 Apr 2011 12:10:46 +0530
From: "Subhasish Ghosh" <subhasish@...tralsolutions.com>
To: "Arnd Bergmann" <arnd@...db.de>
Cc: <linux-arm-kernel@...ts.infradead.org>,
<davinci-linux-open-source@...ux.davincidsp.com>,
<sachi@...tralsolutions.com>,
"Samuel Ortiz" <sameo@...ux.intel.com>, <nsekhar@...com>,
"open list" <linux-kernel@...r.kernel.org>, <m-watkins@...com>,
"Marc Kleine-Budde" <mkl@...gutronix.de>,
"Stalin Srinivasan" <stalin.s@...tralsolutions.com>
Subject: Re: [PATCH v3 1/7] mfd: add pruss mfd driver.
> On Wednesday 30 March 2011, Subhasish Ghosh wrote:
>>
>> >> +s32 pruss_disable(struct device *dev, u8 pruss_num)
>> >> +{
>> >> + struct da8xx_pruss *pruss = dev_get_drvdata(dev->parent);
>> >> + struct da8xx_prusscore_regs *h_pruss;
>> >> + struct pruss_map *pruss_mmap = (struct pruss_map *)pruss->ioaddr;
>> >> + u32 temp_reg;
>> >> + u32 delay_cnt;
>> >
>> > Can you explain the significance of pruss_num? As far as I
>> > can tell, you always pass constants in here, so it should
>> > be possible to determine the number from the device.
>>
>> SG - The number is not programmed in the device, I need something to
>> decide
>> which PRU to disable or enable.
>
> I still don't understand. Please explain how the devices
> relate to the multiple PRUs in hardware.
There are two devices, CAN and UART, in our case we use the PRU as follows:
1. CAN-TX on PRU0, CAN-RX on PRU1
2. SUART-TX on PRU0, SUART-RX on PRU1
3. SUART-TXRX on PRU0, SUART-TXRX on PRU1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists