From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935246AbcKNHER convert rfc822-to-8bit (ORCPT ); Mon, 14 Nov 2016 02:04:17 -0500 Received: from rtits2.realtek.com ([211.75.126.72]:37343 "EHLO rtits2.realtek.com.tw" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934850AbcKNHEJ (ORCPT ); Mon, 14 Nov 2016 02:04:09 -0500 Authenticated-By: X-SpamFilter-By: BOX Solutions SpamTrap 5.56 with qID uAE73pqj024734, This message is accepted by code: ctloc85258 From: Hayes Wang To: David Miller CC: "netdev@vger.kernel.org" , nic_swsd , "linux-kernel@vger.kernel.org" , "linux-usb@vger.kernel.org" , "mlord@pobox.com" Subject: RE: [PATCH net 2/2] r8152: rx descriptor check Thread-Topic: [PATCH net 2/2] r8152: rx descriptor check Thread-Index: AQHSO+t5Wscn8cAer0W3mKS4Fv3VhKDWq+8AgAFde2A= Date: Mon, 14 Nov 2016 07:03:51 +0000 Message-ID: <0835B3720019904CB8F7AA43166CEEB20104EB65@RTITMBSV03.realtek.com.tw> References: <1394712342-15778-226-Taiwan-albertk@realtek.com> <1394712342-15778-228-Taiwan-albertk@realtek.com> <20161113.123954.2134945576362221851.davem@davemloft.net> In-Reply-To: <20161113.123954.2134945576362221851.davem@davemloft.net> Accept-Language: zh-TW, en-US Content-Language: zh-TW X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.21.177.128] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org David Miller [mailto:davem@davemloft.net] > Sent: Monday, November 14, 2016 1:40 AM [...] > If you add this patch now, there is a much smaller likelyhood that you > will work with a high priority to figure out _why_ this is happening. > > For all we know this could be a platform bug in the DMA API for the > systems in question. > > It could also be a bug elsewhere in the driver, either in setting up > the descriptor DMA mappings or how the chip is programmed. > > Either way the true cause must be found before we start throwing > changes like this into the driver. Our hw engineer could check our device, and I could check the driver. However, for the other parts, such as the USB host controller or memory, it is difficult for me to make sure whether they are correct or not. I could only promise our devices and driver work fine. Best Regards, Hayes