From: Mark Rutland <mark.rutland@arm.com> To: Simon Horman <horms@verge.net.au> Cc: Valentine Barshak <valentine.barshak@cogentembedded.com>, "linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>, "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>, Magnus Damm <magnus.damm@gmail.com>, Tejun Heo <tj@kernel.org>, Vladimir Barinov <vladimir.barinov@cogentembedded.com>, Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>, Laurent Pinchart <laurent.pinchart@ideasonboard.com>, Guennadi Liakhovetski <g.liakhovetski@gmx.de>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org> Subject: Re: [PATCH] ata: sata_rcar: Add RCAR Gen2 SATA PHY support Date: Fri, 11 Oct 2013 09:41:57 +0000 [thread overview] Message-ID: <20131011094156.GF3910@e106331-lin.cambridge.arm.com> (raw) In-Reply-To: <20131011010032.GA13809@verge.net.au> On Fri, Oct 11, 2013 at 02:00:35AM +0100, Simon Horman wrote: > [ CCed devicetree@vger.kernel.org as this involves DT compatibility strings ] Cheers! > > On Thu, Oct 10, 2013 at 11:08:03PM +0400, Valentine Barshak wrote: > > RCAR Gen2 SoC has a different phy which is not compatible with > > the older H1/M1 versions. This adds OF/platform device table > > and PHY initialization callbacks for H2/M2 (Gen2) SoC. Is the PHY combined with the rest of the controller, or are they logically separate components in the SoC? I note that the Calxeda Highbank SATA controller driver treats the phy and the controller as separate entities, and describes the way the two are attached (though the driver handles both). Would a similar approach work here? [...] > > +static struct of_device_id sata_rcar_match[] = { > > + { > > + .compatible = "renesas,rcar-sata", > > + .data = (void *)RCAR_SATA > > + }, > > + { > > + .compatible = "renesas,sata-r8a7790", > > + .data = (void *)RCAR_GEN2_SATA > > + }, > > + { > > + .compatible = "renesas,sata-r8a7791", > > + .data = (void *)RCAR_GEN2_SATA > > + }, > > + {}, These bindings will need documentation. A grep of any of these in mainline's Documentation/devicetree shows up nothing (not even the existing "renesas,rcar-sata" string used by the driver. Thanks, Mark.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland@arm.com> To: Simon Horman <horms@verge.net.au> Cc: Valentine Barshak <valentine.barshak@cogentembedded.com>, "linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>, "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>, Magnus Damm <magnus.damm@gmail.com>, Tejun Heo <tj@kernel.org>, Vladimir Barinov <vladimir.barinov@cogentembedded.com>, Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>, Laurent Pinchart <laurent.pinchart@ideasonboard.com>, Guennadi Liakhovetski <g.liakhovetski@gmx.de>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org> Subject: Re: [PATCH] ata: sata_rcar: Add RCAR Gen2 SATA PHY support Date: Fri, 11 Oct 2013 10:41:57 +0100 [thread overview] Message-ID: <20131011094156.GF3910@e106331-lin.cambridge.arm.com> (raw) In-Reply-To: <20131011010032.GA13809@verge.net.au> On Fri, Oct 11, 2013 at 02:00:35AM +0100, Simon Horman wrote: > [ CCed devicetree@vger.kernel.org as this involves DT compatibility strings ] Cheers! > > On Thu, Oct 10, 2013 at 11:08:03PM +0400, Valentine Barshak wrote: > > RCAR Gen2 SoC has a different phy which is not compatible with > > the older H1/M1 versions. This adds OF/platform device table > > and PHY initialization callbacks for H2/M2 (Gen2) SoC. Is the PHY combined with the rest of the controller, or are they logically separate components in the SoC? I note that the Calxeda Highbank SATA controller driver treats the phy and the controller as separate entities, and describes the way the two are attached (though the driver handles both). Would a similar approach work here? [...] > > +static struct of_device_id sata_rcar_match[] = { > > + { > > + .compatible = "renesas,rcar-sata", > > + .data = (void *)RCAR_SATA > > + }, > > + { > > + .compatible = "renesas,sata-r8a7790", > > + .data = (void *)RCAR_GEN2_SATA > > + }, > > + { > > + .compatible = "renesas,sata-r8a7791", > > + .data = (void *)RCAR_GEN2_SATA > > + }, > > + {}, These bindings will need documentation. A grep of any of these in mainline's Documentation/devicetree shows up nothing (not even the existing "renesas,rcar-sata" string used by the driver. Thanks, Mark.
next prev parent reply other threads:[~2013-10-11 9:41 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-10 19:08 [PATCH] ata: sata_rcar: Add RCAR Gen2 SATA PHY support Valentine Barshak 2013-10-10 19:08 ` Valentine Barshak 2013-10-11 1:00 ` Simon Horman 2013-10-11 1:00 ` Simon Horman 2013-10-11 9:41 ` Mark Rutland [this message] 2013-10-11 9:41 ` Mark Rutland 2013-10-11 10:54 ` Valentine 2013-10-11 10:54 ` Valentine 2013-10-11 14:47 ` Mark Rutland 2013-10-11 14:47 ` Mark Rutland 2013-10-11 15:14 ` Valentine 2013-10-11 15:14 ` Valentine 2013-10-11 9:53 ` Valentine 2013-10-11 9:53 ` Valentine 2013-10-11 19:25 ` Sergei Shtylyov 2013-10-11 20:24 ` Sergei Shtylyov
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20131011094156.GF3910@e106331-lin.cambridge.arm.com \ --to=mark.rutland@arm.com \ --cc=devicetree@vger.kernel.org \ --cc=g.liakhovetski@gmx.de \ --cc=horms@verge.net.au \ --cc=kuninori.morimoto.gx@renesas.com \ --cc=laurent.pinchart@ideasonboard.com \ --cc=linux-ide@vger.kernel.org \ --cc=linux-sh@vger.kernel.org \ --cc=magnus.damm@gmail.com \ --cc=tj@kernel.org \ --cc=valentine.barshak@cogentembedded.com \ --cc=vladimir.barinov@cogentembedded.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.