From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964901AbbJ0PDz (ORCPT ); Tue, 27 Oct 2015 11:03:55 -0400 Received: from foss.arm.com ([217.140.101.70]:56979 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932256AbbJ0PDw (ORCPT ); Tue, 27 Oct 2015 11:03:52 -0400 Date: Tue, 27 Oct 2015 15:03:41 +0000 From: Mark Rutland To: zhangfei Cc: John Garry , JBottomley@odin.com, robh+dt@kernel.org, pawel.moll@arm.com, ijc+devicetree@hellion.org.uk, galak@codeaurora.org, arnd@arndb.de, linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linuxarm@huawei.com, john.garry2@mail.dcu.ie, hare@suse.de, xuwei5@hisilicon.com Subject: Re: [PATCH v2 02/32] devicetree: bindings: scsi: HiSi SAS Message-ID: <20151027150341.GH3091@leverpostej> References: <1445868903-183817-1-git-send-email-john.garry@huawei.com> <1445868903-183817-3-git-send-email-john.garry@huawei.com> <20151026144523.GB12277@leverpostej> <562F777B.6020407@huawei.com> <20151027143939.GG3091@leverpostej> <562F9016.50807@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <562F9016.50807@linaro.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > >>>>+ - ctrl-reg : offset to the following SAS control registers (in order): > >>>>+ - reset assert > >>>>+ - clock disable > >>>>+ - reset status > >>>>+ - reset de-assert > >>>>+ - clock enable [...] > >It would be better to have each offset in a separate property. > > > These register are not used for different purpose. > Instead, they are all used for one purpose, reset the sas controller; > Though a bit complicated, the silicon has special requirement here. While they are indeed used together, they are separate registers, as listed above. There may be other registers in future that turn out to be useful for the SAS controller, or it might turn out a new system doesn't have all of the existing registers. > So still prefer using the original method, > ctrl-reg = <0xa60 0x33c 0x5a30 0xa64 0x338>; > Since we can simply use of_property_read_u32_array. That may be simpler now, but makes future maintenance harder. Use separate properties. Mark.