From: Marek Vasut <marex@denx.de>
To: Austin Boyle <boyle.austin@gmail.com>
Cc: Angus Clark <angus.clark@st.com>,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
Gerlando Falauto <gerlando.falauto@keymile.com>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH v3] mtd: m25p80: Calculate flash block protect bits based on number of sectors
Date: Thu, 17 Apr 2014 01:22:20 +0200 [thread overview]
Message-ID: <201404170122.20996.marex@denx.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1404162227120.3848@austin-Satellite-L510>
On Wednesday, April 16, 2014 at 02:37:13 PM, Austin Boyle wrote:
> This patch generalises the calculation of block protect bits based on the
> number of sectors and implements the _is_locked function.
>
> Existing calculation of block protect bits only works for devices with 64
> sectors or more. This new logic is applicable to the STmicro devices:
> m25p10, p20, p40, p80, p16, pe16, p32, p64, p128.
> Note devices with >64 sectors only allow the protected region to be
> specified to a resolution of 1/64th of the total size (such as m25p64).
>
> New return codes for ioctl(MEMISLOCKED) have been added to
> uapi/mtd/mtd-abi.h because the _is_locked function can query a region
> which is partially unlocked.
>
> Added flag to m25p_ids table to indicate if flash protection is supported.
>
> Added n_sectors and sector_size to m25p flash structure so it can be used
> in block protect bit calculation.
>
> From: Austin Boyle <boyle.austin@gmail.com>
> Signed-off-by: Austin Boyle <boyle.austin@gmail.com>
Acked-by: Marek Vasut <marex@denx.de>
Thanks!
Best regards,
Marek Vasut
WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marex@denx.de>
To: Austin Boyle <boyle.austin@gmail.com>
Cc: Brian Norris <computersforpeace@gmail.com>,
Gerlando Falauto <gerlando.falauto@keymile.com>,
linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
Angus Clark <angus.clark@st.com>
Subject: Re: [PATCH v3] mtd: m25p80: Calculate flash block protect bits based on number of sectors
Date: Thu, 17 Apr 2014 01:22:20 +0200 [thread overview]
Message-ID: <201404170122.20996.marex@denx.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1404162227120.3848@austin-Satellite-L510>
On Wednesday, April 16, 2014 at 02:37:13 PM, Austin Boyle wrote:
> This patch generalises the calculation of block protect bits based on the
> number of sectors and implements the _is_locked function.
>
> Existing calculation of block protect bits only works for devices with 64
> sectors or more. This new logic is applicable to the STmicro devices:
> m25p10, p20, p40, p80, p16, pe16, p32, p64, p128.
> Note devices with >64 sectors only allow the protected region to be
> specified to a resolution of 1/64th of the total size (such as m25p64).
>
> New return codes for ioctl(MEMISLOCKED) have been added to
> uapi/mtd/mtd-abi.h because the _is_locked function can query a region
> which is partially unlocked.
>
> Added flag to m25p_ids table to indicate if flash protection is supported.
>
> Added n_sectors and sector_size to m25p flash structure so it can be used
> in block protect bit calculation.
>
> From: Austin Boyle <boyle.austin@gmail.com>
> Signed-off-by: Austin Boyle <boyle.austin@gmail.com>
Acked-by: Marek Vasut <marex@denx.de>
Thanks!
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-04-16 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 12:37 [PATCH v3] mtd: m25p80: Calculate flash block protect bits based on number of sectors Austin Boyle
2014-04-16 12:37 ` Austin Boyle
2014-04-16 23:22 ` Marek Vasut [this message]
2014-04-16 23:22 ` Marek Vasut
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=201404170122.20996.marex@denx.de \
--to=marex@denx.de \
--cc=angus.clark@st.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=boyle.austin@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=gerlando.falauto@keymile.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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 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.