From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752927AbcEYJ7o (ORCPT ); Wed, 25 May 2016 05:59:44 -0400 Received: from mail-am1on0096.outbound.protection.outlook.com ([157.56.112.96]:52179 "EHLO emea01-am1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750720AbcEYJ7m convert rfc822-to-8bit (ORCPT ); Wed, 25 May 2016 05:59:42 -0400 X-Greylist: delayed 25901 seconds by postgrey-1.27 at vger.kernel.org; Wed, 25 May 2016 05:59:42 EDT From: Meng Yi To: Mark Brown CC: "dri-devel@lists.freedesktop.org" , "David Airlie" , Stefan Agner , "airlied@redhat.com" , "linux-kernel@vger.kernel.org" Subject: RE: fsl-dcu not works on latest "drm-next" Thread-Topic: fsl-dcu not works on latest "drm-next" Thread-Index: AdGlFm3AneZxjhLuSCG3KXnHNBlzPgREwk9wAA88lAAAAHr0gA== Date: Wed, 25 May 2016 09:59:39 +0000 Message-ID: References: <20160525091834.GQ8206@sirena.org.uk> In-Reply-To: <20160525091834.GQ8206@sirena.org.uk> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: kernel.org; dkim=none (message not signed) header.d=none;kernel.org; dmarc=none action=none header.from=nxp.com; x-originating-ip: [192.158.241.86] x-ms-office365-filtering-correlation-id: 84631b16-54fe-4ee7-e004-08d38483496b x-microsoft-exchange-diagnostics: 1;HE1PR04MB1049;5:ODYpkqRp2dUzF00qP+w8iElXltjisurAKfbqoTCC+0KF/qFnhy1oLWdJHthjOaqjWm/LwPaHbgUQbm477BGkqruJ2UzmH+XVkZXm8deMKU0/CHkEDV9T1EpgevGh/MHsghBWT1wl9mcQfs1jgJ2vOg==;24:danAkvW8GpPw0rmUmPHSfSkS0nZkTRBYQN0Sapj0lELo98qwc0h2rXut0nS3ML/6nJ9u+XZgD1moXBy3/3avb7bu4YK1CHDicEbHBA4ZmOw=;7:VP/h4ThriSDbLrnccwEQ+UjqZ9QZg6flcEGE16UoEnaASH0V49OU1J55aBzmINRuRX3eqhcgDhVVTw6UacE1l1yrlqFAj9E6g7BNf+l68T1bADrwcLgEIBZCTuC9mbRnCPcVBg9YiqxldxcHbxjYYFuNC6peQLMmMQ5bFi3VjuA2PoaUpfgprzMBEwSo897j x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:HE1PR04MB1049; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026);SRVR:HE1PR04MB1049;BCL:0;PCL:0;RULEID:;SRVR:HE1PR04MB1049; x-forefront-prvs: 09538D3531 x-forefront-antispam-report: SFV:NSPM;SFS:(10009020)(6009001)(122556002)(3660700001)(33656002)(5003600100002)(2906002)(4326007)(77096005)(81166006)(8676002)(8936002)(9686002)(11100500001)(5004730100002)(2900100001)(3846002)(586003)(6116002)(102836003)(1220700001)(3280700002)(76576001)(2950100001)(50986999)(86362001)(74316001)(54356999)(76176999)(87936001)(10400500002)(110136002)(189998001)(66066001)(92566002)(5008740100001)(5002640100001);DIR:OUT;SFP:1101;SCL:1;SRVR:HE1PR04MB1049;H:HE1PR04MB1051.eurprd04.prod.outlook.com;FPR:;SPF:None;MLV:sfv;LANG:en; spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 X-OriginatorOrg: nxp.com X-MS-Exchange-CrossTenant-originalarrivaltime: 25 May 2016 09:59:39.4416 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 686ea1d3-bc2b-4c6f-a92c-d99c5c301635 X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR04MB1049 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Mark, > > Without any description of the problem it is difficult to comment. > There were some drivers that were abusing the API by hacking round things > that need fixing (the main one I've seen is reporting things as big endian > instead of native endian to cause two layers of translation to kick in) and one > that was trying to use regmap to represent something that just fundamentally > wasn't a regmap so *any* change in regmap internals was risky. I was testing HDMI patches on latest "drm-next" branch, and found that it is not work. And then I found the base tree was not working too. Then I debugged the base tree. I read out the value of relevant register using "CodeWarrior TAP", find that endianness is not right. Then I changed endianness of the value to be written that using " regmap_write" . It works. But "regmap_update_bits" still have the problem. I had checked log of regmap, and didn't find which commit caused that. I am not familiar with regmap, can you give some advices? Thanks, Best Regards, Meng Yi