linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: Kamal Dasu <kdasu.kdev@gmail.com>
Cc: Marek Vasut <marex@denx.de>,
	Florian Fainelli <f.fainelli@gmail.com>,
	linux-spi <linux-spi@vger.kernel.org>,
	Mark Brown <broonie@kernel.org>,
	bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	Cyrille Pitchen <cyrille.pitchen@atmel.com>
Subject: Re: [PATCH v4 1/2] mtd: spi-nor: Added spi-nor init function
Date: Mon, 20 Feb 2017 09:12:08 +0100	[thread overview]
Message-ID: <CACna6rzV3xNSyGGmDvTvbfMVp=iAZdXBQpniKFULKOtBW_6aow@mail.gmail.com> (raw)
In-Reply-To: <1487086368-4118-2-git-send-email-kdasu.kdev@gmail.com>

On 14 February 2017 at 16:32, Kamal Dasu <kdasu.kdev@gmail.com> wrote:
> Refactored spi_nor_scan() code to add spi_nor_init() function that
> programs the spi-nor flash to:
> 1) remove flash protection if applicable
> 2) set read mode to quad mode if configured such
> 3) set the address width based on the flash size and vendor
>
> spi_nor_scan() now calls spi_nor_init() to setup nor flash.
>
> Signed-off-by: Kamal Dasu <kdasu.kdev@gmail.com>

Ideally a short reason info should go there.
"This allows reusing spi_nor_init during resume"
or whatever :)

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  parent reply	other threads:[~2017-02-20  8:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 15:32 [PATCH v4 0/2] Added support for spi-nor device pm in m25p80 Kamal Dasu
     [not found] ` <1487086368-4118-1-git-send-email-kdasu.kdev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-02-14 15:32   ` [PATCH v4 1/2] mtd: spi-nor: Added spi-nor init function Kamal Dasu
     [not found]     ` <1487086368-4118-2-git-send-email-kdasu.kdev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-02-18 22:29       ` Marek Vasut
     [not found]         ` <b6079dbb-82fc-7579-32b2-b8c071ef02ef-ynQEQJNshbs@public.gmane.org>
2017-02-19  9:47           ` Kamal Dasu
     [not found]             ` <CAKekbesKKS_s873D=xy2tQcVYei_26gYipn2ru1rVY4ihXbsXw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-19 10:37               ` Marek Vasut
     [not found]                 ` <54393706-cd93-603a-193b-25fbf52b2d83-ynQEQJNshbs@public.gmane.org>
2017-02-19 22:38                   ` Kamal Dasu
     [not found]                     ` <CAKekbetnpY=zRJM0=xn5t2enDcts5tQTV6ZtvPaW_geOd3=DQQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-19 22:51                       ` Marek Vasut
2017-02-20  8:12     ` Rafał Miłecki [this message]
2017-02-20  8:15       ` Marek Vasut
2017-02-14 15:32   ` [PATCH v4 2/2] mtd: m25p80: Added pm ops support Kamal Dasu
     [not found]     ` <1487086368-4118-3-git-send-email-kdasu.kdev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-02-18 22:31       ` Marek Vasut
     [not found]         ` <e5fb0bdf-0956-e364-14fb-c255471f371d-ynQEQJNshbs@public.gmane.org>
2017-02-19  9:48           ` Kamal Dasu

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='CACna6rzV3xNSyGGmDvTvbfMVp=iAZdXBQpniKFULKOtBW_6aow@mail.gmail.com' \
    --to=zajec5@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=broonie@kernel.org \
    --cc=cyrille.pitchen@atmel.com \
    --cc=f.fainelli@gmail.com \
    --cc=kdasu.kdev@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=marex@denx.de \
    /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).