devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	linux-crypto@vger.kernel.org,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	Horia Geanta Neag <horia.geanta@nxp.com>,
	Fabio Estevam <fabio.estevam@nxp.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: fsl-imx-sahara: Add i.MX51 as a supported SoC
Date: Mon, 25 Jun 2018 17:27:51 -0300	[thread overview]
Message-ID: <CAOMZO5AAmC9_2RDu4_omCFLazV2Q083vPkCbH+_gie_jZnMp5A@mail.gmail.com> (raw)
In-Reply-To: <20180625202109.GA22892@rob-hp-laptop>

Hi Rob,

On Mon, Jun 25, 2018 at 5:21 PM, Rob Herring <robh@kernel.org> wrote:

> Looks like imx51 should be a fallback and you can drop the driver
> change.

I thought about that too.

If I do like this in imx51.dtsi:

compatible = "fsl,imx51-sahara", "fsl,imx53-sahara";

Then the driver works just fine.

I was not sure if this was OK or not because imx51 was introduced
prior than imx53 was launched.

Would it be OK to use: compatible = "fsl,imx51-sahara", "fsl,imx53-sahara"; ?

Thanks

  reply	other threads:[~2018-06-25 20:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22 18:45 [PATCH v2 1/2] dt-bindings: fsl-imx-sahara: Add i.MX51 as a supported SoC Fabio Estevam
2018-06-22 18:45 ` [PATCH v2 2/2] crypto: sahara - Add i.MX51 entry Fabio Estevam
2018-06-25 20:21 ` [PATCH v2 1/2] dt-bindings: fsl-imx-sahara: Add i.MX51 as a supported SoC Rob Herring
2018-06-25 20:27   ` Fabio Estevam [this message]
2018-06-26 14:24     ` Rob Herring
2018-06-26 23:19       ` Fabio Estevam

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=CAOMZO5AAmC9_2RDu4_omCFLazV2Q083vPkCbH+_gie_jZnMp5A@mail.gmail.com \
    --to=festevam@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=horia.geanta@nxp.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=robh@kernel.org \
    /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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).