From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?44Kr44Kq44CA44Of44Oz44CA44OS44Kn44OD44OX?= Date: Mon, 17 Mar 2014 12:01:40 +0000 Subject: Re: [RFC] spi: Using Trigger number to transmit/receive data Message-Id: <5326E424.9040709@jinso.co.jp> List-Id: References: <1394699364-5669-1-git-send-email-cm-hiep@jinso.co.jp> <1394699364-5669-2-git-send-email-cm-hiep@jinso.co.jp> <53264BA4.3000401@jinso.co.jp> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: Geert Uytterhoeven Cc: Mark Brown , "devicetree@vger.kernel.org" , Linux-sh list , Kuninori Morimoto , Geert Uytterhoeven Hi Geert On 03/17/2014 04:54 PM, Geert Uytterhoeven wrote: > Hi Hiep, > > On Mon, Mar 17, 2014 at 2:11 AM, カオ　ミン　ヒェップ wrote: >> On 03/13/2014 06:23 PM, Geert Uytterhoeven wrote: >>> On Thu, Mar 13, 2014 at 9:29 AM, Cao Minh Hiep >>> wrote: >>>> In order to transmit and receive data when have 32 bytes of data that >>>> ready has prepared on Transmit/Receive Buffer to transmit or receive. >>>> Instead transmits/receives a byte data using Transmit/Receive Buffer >>>> Data Triggering Number will improve the speed of transfer data. >>> Thanks for your patch, this looks like a valuable improvement! >>> >>> Unfortunately your patch doesn't apply against spi/for-next anymore, as >>> the driver has changed a lot lately, due to the addition of RZ/A1H and >>> Quad/Dual support. >>> >> Thanks, Do you mean this patch did not need for next and I don't mind about >> it? > It means you will have to rework your patch to apply on top of > https://git.kernel.org/cgit/linux/kernel/git/broonie/spi.git/tree/drivers/spi?h=for-next > before the SPI maintainer can accept it. Thanks, I understood, I will rework my patch and report to your later. Cao Minh Hiep. From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?44Kr44Kq44CA44Of44Oz44CA44OS44Kn44OD44OX?= Subject: Re: [RFC] spi: Using Trigger number to transmit/receive data Date: Mon, 17 Mar 2014 21:01:40 +0900 Message-ID: <5326E424.9040709@jinso.co.jp> References: <1394699364-5669-1-git-send-email-cm-hiep@jinso.co.jp> <1394699364-5669-2-git-send-email-cm-hiep@jinso.co.jp> <53264BA4.3000401@jinso.co.jp> Reply-To: cm-hiep@jinso.co.jp Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: Sender: linux-sh-owner@vger.kernel.org To: Geert Uytterhoeven Cc: Mark Brown , "devicetree@vger.kernel.org" , Linux-sh list , Kuninori Morimoto , Geert Uytterhoeven List-Id: devicetree@vger.kernel.org Hi Geert On 03/17/2014 04:54 PM, Geert Uytterhoeven wrote: > Hi Hiep, > > On Mon, Mar 17, 2014 at 2:11 AM, =E3=82=AB=E3=82=AA=E3=80=80=E3=83=9F= =E3=83=B3=E3=80=80=E3=83=92=E3=82=A7=E3=83=83=E3=83=97 wrote: >> On 03/13/2014 06:23 PM, Geert Uytterhoeven wrote: >>> On Thu, Mar 13, 2014 at 9:29 AM, Cao Minh Hiep >>> wrote: >>>> In order to transmit and receive data when have 32 bytes of data t= hat >>>> ready has prepared on Transmit/Receive Buffer to transmit or recei= ve. >>>> Instead transmits/receives a byte data using Transmit/Receive Buff= er >>>> Data Triggering Number will improve the speed of transfer data. >>> Thanks for your patch, this looks like a valuable improvement! >>> >>> Unfortunately your patch doesn't apply against spi/for-next anymore= , as >>> the driver has changed a lot lately, due to the addition of RZ/A1H = and >>> Quad/Dual support. >>> >> Thanks, Do you mean this patch did not need for next and I don't min= d about >> it? > It means you will have to rework your patch to apply on top of > https://git.kernel.org/cgit/linux/kernel/git/broonie/spi.git/tree/dri= vers/spi?h=3Dfor-next > before the SPI maintainer can accept it. Thanks, I understood, I will rework my patch and report to your later. Cao Minh Hiep.