From mboxrd@z Thu Jan 1 00:00:00 1970 From: Simon Horman Subject: Re: [PATCH] SATA: rcar: add device tree support for r8a7792 Date: Tue, 8 Mar 2016 10:32:30 +0900 Message-ID: <20160308013230.GA19428@verge.net.au> References: <1456362985-24137-1-git-send-email-horms+renesas@verge.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1456362985-24137-1-git-send-email-horms+renesas@verge.net.au> Sender: linux-renesas-soc-owner@vger.kernel.org To: Tejun Heo Cc: linux-ide@vger.kernel.org, linux-renesas-soc@vger.kernel.org, Magnus Damm , devicetree@vger.kernel.org List-Id: devicetree@vger.kernel.org On Thu, Feb 25, 2016 at 10:16:25AM +0900, Simon Horman wrote: > Simply document new compatibility string. > As a previous patch adds a generic R-Car Gen2 compatibility string > there appears to be no need for a driver updates. > > By documenting this compat sting it may be used in DTSs shipped, for > example as part of ROMs. It must be used in conjunction with the Gen2 > fallback compat string. At this time there are no known differences between > the r8a7792 IP block and that implemented by the driver for the Gen2 > fallback compat string. Thus there is no need to update the driver as the > use of the Gen2 fallback compat string will activate the correct code in > the current driver while leaving the option for r8a7792-specific driver > code to be activated in an updated driver should the need arise. > > Signed-off-by: Simon Horman > --- > Documentation/devicetree/bindings/ata/sata_rcar.txt | 1 + > 1 file changed, 1 insertion(+) > > Based on the for-next branch of the libata tree I would like to withdraw this patch. On closer inspection of the documentation the SATA IP block does not appear to be present on the r8a7792. I am now searching for an appropriately sized brown paper bag.