From: "Langer, Thomas" <thomas.langer@intel.com>
To: Seb <sebtx452@gmail.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: RE: [PATCH] mtd: maps: lantiq-flash: Check if the EBU endianness swap is enabled
Date: Thu, 26 Jan 2017 16:01:04 +0000 [thread overview]
Message-ID: <0DAF21CFE1B20740AE23D6AF6E54843F1E6F9DE6@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <CA+hF=GcW2W6T08BZYXoZQcpe=+QuPp0H7kT2ci+6Td-ZZL+ouQ@mail.gmail.com>
Hi Sebastian,
>
> > We should introduce specific compatible strings for this driver, which
> trigger this,
> > e.g. "lantiq,nor-vr9" or "lantiq,nor-ar10" (or better using family names
> "xrx200" and "xrx300")
>
> You mean we can use the same way as other drivers, for example in the
> physmap_of_versatile.c file :
>
> static const struct of_device_id syscon_match[] = {
> {
> .compatible = "arm,integrator-ap-syscon",
> .data = (void *)INTEGRATOR_AP_FLASHPROT,
> },
> {
> .compatible = "arm,integrator-cp-syscon",
> .data = (void *)INTEGRATOR_CP_FLASHPROT,
> },
>
> etc...
>
>
> We can't filter on xrx200 or vr9, but we have to know the VR9 version
> (as the VR9 < 1.2 is not compatible with this patch).
Then extend the compatible strings with versions (where necessary).
This requires to know the SoC version for each board, but it should be
okay and is done for other system already this way.
>
> Regards,
>
> Sebastien
Regards,
Thomas
next prev parent reply other threads:[~2017-01-26 16:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 9:33 [PATCH] mtd: maps: lantiq-flash: Check if the EBU endianness swap is enabled Sebastien Decourriere
2017-01-24 17:03 ` Ralf Baechle
2017-01-24 21:32 ` Hauke Mehrtens
2017-01-25 9:04 ` Seb
2017-01-25 16:58 ` Langer, Thomas
2017-01-26 11:02 ` Seb
2017-01-26 16:01 ` Langer, Thomas [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-19 10:06 Sebastien Decourriere
2017-01-19 23:50 ` Langer, Thomas
2017-01-18 12:10 Sebastien Decourriere
2017-01-18 12:38 ` John Crispin
2017-01-18 13:48 ` Seb
2017-01-18 13:51 ` John Crispin
2017-01-18 17:12 ` Seb
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=0DAF21CFE1B20740AE23D6AF6E54843F1E6F9DE6@IRSMSX101.ger.corp.intel.com \
--to=thomas.langer@intel.com \
--cc=hauke@hauke-m.de \
--cc=linux-mips@linux-mips.org \
--cc=linux-mtd@lists.infradead.org \
--cc=sebtx452@gmail.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: 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).