All of lore.kernel.org
 help / color / mirror / Atom feed
From: Huang Shijie <shijie8@gmail.com>
To: "Gupta, Pekon" <pekon@ti.com>
Cc: "angus.clark@st.com" <angus.clark@st.com>,
	Shawn Guo <shawn.guo@linaro.org>,
	"b44548@freescale.com" <b44548@freescale.com>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Mark Brown <broonie@linaro.org>,
	"b18965@freescale.com" <b18965@freescale.com>,
	"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
	Huang Shijie <b32955@freescale.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"Poddar, Sourav" <sourav.poddar@ti.com>,
	Brian Norris <computersforpeace@gmail.com>,
	Lee Jones <lee.jones@linaro.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Jagan Teki <jagannadh.teki@gmail.com>
Subject: Re: [PATCH v4 0/7] mtd: spi-nor: add a new framework for SPI NOR
Date: Sun, 19 Jan 2014 10:44:06 +0800	[thread overview]
Message-ID: <20140119024405.GA2321@gmail.com> (raw)
In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73EA664C6@DBDE04.ent.ti.com>

On Fri, Jan 17, 2014 at 05:40:09PM +0000, Gupta, Pekon wrote:
> Hi Shijie,
> 
> >From: Jagan Teki [mailto:jagannadh.teki@gmail.com]
> [...]
> >
> >I feel these are good points to discuss all.
> >1. With new framework seems like we need two separate controller drivers
> >    one for non spi-nor and one for spi-nor with single controller hw
> >2. With spi-nor implementation though the hw is spi complaint but the sw is
> >   completely ignoring the Linux SPI core interaction.
> >
> >I feel above two points are technically wrong - Please correct me if am wrong
> >but need all developers will join..thanks!
> >
> I have been following this patch-set from sometime, And I think point (2)
> has been discussed back and forth in multiple times in earlier discussions.
> So, Is it possible for you to summarize point (2) with all pros-n-cons ?
> 
> - A README will helpful to clear all doubts and will ease your implementation
>   as well.
> - It will also help in reducing turn-around time to get this framework in
>    acceptable state and still keep it generic enough.
> 
> You can submit the README as Documentation/mtd/spi-nor.txt
okay.

thanks
Huang Shijie

WARNING: multiple messages have this Message-ID (diff)
From: Huang Shijie <shijie8@gmail.com>
To: "Gupta, Pekon" <pekon@ti.com>
Cc: Huang Shijie <b32955@freescale.com>,
	"angus.clark@st.com" <angus.clark@st.com>,
	Brian Norris <computersforpeace@gmail.com>,
	"b44548@freescale.com" <b44548@freescale.com>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	Lee Jones <lee.jones@linaro.org>, Mark Brown <broonie@linaro.org>,
	"b18965@freescale.com" <b18965@freescale.com>,
	"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"Poddar, Sourav" <sourav.poddar@ti.com>,
	Shawn Guo <shawn.guo@linaro.org>,
	David Woodhouse <dwmw2@infradead.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Jagan Teki <jagannadh.teki@gmail.com>
Subject: Re: [PATCH v4 0/7] mtd: spi-nor: add a new framework for SPI NOR
Date: Sun, 19 Jan 2014 10:44:06 +0800	[thread overview]
Message-ID: <20140119024405.GA2321@gmail.com> (raw)
In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73EA664C6@DBDE04.ent.ti.com>

On Fri, Jan 17, 2014 at 05:40:09PM +0000, Gupta, Pekon wrote:
> Hi Shijie,
> 
> >From: Jagan Teki [mailto:jagannadh.teki@gmail.com]
> [...]
> >
> >I feel these are good points to discuss all.
> >1. With new framework seems like we need two separate controller drivers
> >    one for non spi-nor and one for spi-nor with single controller hw
> >2. With spi-nor implementation though the hw is spi complaint but the sw is
> >   completely ignoring the Linux SPI core interaction.
> >
> >I feel above two points are technically wrong - Please correct me if am wrong
> >but need all developers will join..thanks!
> >
> I have been following this patch-set from sometime, And I think point (2)
> has been discussed back and forth in multiple times in earlier discussions.
> So, Is it possible for you to summarize point (2) with all pros-n-cons ?
> 
> - A README will helpful to clear all doubts and will ease your implementation
>   as well.
> - It will also help in reducing turn-around time to get this framework in
>    acceptable state and still keep it generic enough.
> 
> You can submit the README as Documentation/mtd/spi-nor.txt
okay.

thanks
Huang Shijie

WARNING: multiple messages have this Message-ID (diff)
From: shijie8@gmail.com (Huang Shijie)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/7] mtd: spi-nor: add a new framework for SPI NOR
Date: Sun, 19 Jan 2014 10:44:06 +0800	[thread overview]
Message-ID: <20140119024405.GA2321@gmail.com> (raw)
In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73EA664C6@DBDE04.ent.ti.com>

On Fri, Jan 17, 2014 at 05:40:09PM +0000, Gupta, Pekon wrote:
> Hi Shijie,
> 
> >From: Jagan Teki [mailto:jagannadh.teki at gmail.com]
> [...]
> >
> >I feel these are good points to discuss all.
> >1. With new framework seems like we need two separate controller drivers
> >    one for non spi-nor and one for spi-nor with single controller hw
> >2. With spi-nor implementation though the hw is spi complaint but the sw is
> >   completely ignoring the Linux SPI core interaction.
> >
> >I feel above two points are technically wrong - Please correct me if am wrong
> >but need all developers will join..thanks!
> >
> I have been following this patch-set from sometime, And I think point (2)
> has been discussed back and forth in multiple times in earlier discussions.
> So, Is it possible for you to summarize point (2) with all pros-n-cons ?
> 
> - A README will helpful to clear all doubts and will ease your implementation
>   as well.
> - It will also help in reducing turn-around time to get this framework in
>    acceptable state and still keep it generic enough.
> 
> You can submit the README as Documentation/mtd/spi-nor.txt
okay.

thanks
Huang Shijie

  reply	other threads:[~2014-01-19  2:44 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-25  5:50 [PATCH v4 0/7] mtd: spi-nor: add a new framework for SPI NOR Huang Shijie
2013-12-25  5:50 ` Huang Shijie
2013-12-25  5:50 ` Huang Shijie
2013-12-25  5:50 ` Huang Shijie
2013-12-25  5:50 ` [PATCH v4 1/7] mtd: spi-nor: copy the SPI NOR commands to a new header file Huang Shijie
2013-12-25  5:50   ` Huang Shijie
2013-12-25  5:50   ` Huang Shijie
2013-12-25  5:50   ` Huang Shijie
2013-12-25  5:50 ` [PATCH v4 2/7] mtd: spi-nor: add the basic data structures Huang Shijie
2013-12-25  5:50   ` Huang Shijie
2013-12-25  5:50   ` Huang Shijie
2013-12-25  5:50   ` Huang Shijie
2013-12-25  5:50 ` [PATCH v4 3/7] mtd: spi-nor: add the framework for SPI NOR Huang Shijie
2013-12-25  5:50   ` Huang Shijie
2013-12-25  5:50   ` Huang Shijie
2013-12-25  5:50   ` Huang Shijie
2013-12-25  5:50 ` [PATCH v4 4/7] mtd: m25p80: use the SPI nor framework Huang Shijie
2013-12-25  5:50   ` Huang Shijie
2013-12-25  5:50   ` Huang Shijie
2013-12-25  5:50   ` Huang Shijie
2013-12-25  5:50 ` [PATCH v4 5/7] mtd: spi-nor: add a helper to find the spi_device_id Huang Shijie
2013-12-25  5:50   ` Huang Shijie
2013-12-25  5:50   ` Huang Shijie
2013-12-25  5:50   ` Huang Shijie
2013-12-25  5:50 ` [PATCH v4 6/7] Documentation: add the binding file for Freescale QuadSPI driver Huang Shijie
2013-12-25  5:50   ` Huang Shijie
2013-12-25  5:50   ` Huang Shijie
2013-12-25  5:50   ` Huang Shijie
2013-12-25  5:50 ` [PATCH v4 7/7] mtd: spi-nor: Add " Huang Shijie
2013-12-25  5:50   ` Huang Shijie
2013-12-25  5:50   ` Huang Shijie
2013-12-25  5:50   ` Huang Shijie
2014-01-15 19:15 ` [PATCH v4 0/7] mtd: spi-nor: add a new framework for SPI NOR Jagan Teki
2014-01-15 19:15   ` Jagan Teki
2014-01-15 19:15   ` Jagan Teki
2014-01-16  9:11   ` Huang Shijie
2014-01-16  9:11     ` Huang Shijie
2014-01-16  9:11     ` Huang Shijie
2014-01-16  9:11     ` Huang Shijie
2014-01-16  9:39     ` Jagan Teki
2014-01-16  9:39       ` Jagan Teki
2014-01-16  9:39       ` Jagan Teki
2014-01-17  2:02       ` Huang Shijie
2014-01-17  2:02         ` Huang Shijie
2014-01-17  2:02         ` Huang Shijie
2014-01-17  2:02         ` Huang Shijie
2014-01-17  7:06         ` Jagan Teki
2014-01-17  7:06           ` Jagan Teki
2014-01-17  7:06           ` Jagan Teki
2014-01-17  6:54           ` Huang Shijie
2014-01-17  6:54             ` Huang Shijie
2014-01-17  6:54             ` Huang Shijie
2014-01-17  6:54             ` Huang Shijie
2014-01-17  8:39             ` Jagan Teki
2014-01-17  8:39               ` Jagan Teki
2014-01-17  8:39               ` Jagan Teki
2014-01-17 17:06               ` Jagan Teki
2014-01-17 17:06                 ` Jagan Teki
2014-01-17 17:06                 ` Jagan Teki
2014-01-17 17:40                 ` Gupta, Pekon
2014-01-17 17:40                   ` Gupta, Pekon
2014-01-17 17:40                   ` Gupta, Pekon
2014-01-19  2:44                   ` Huang Shijie [this message]
2014-01-19  2:44                     ` Huang Shijie
2014-01-19  2:44                     ` Huang Shijie
2014-01-19  2:28               ` Huang Shijie
2014-01-19  2:28                 ` Huang Shijie
2014-01-19  2:28                 ` Huang Shijie
2014-01-19 10:09                 ` Jagan Teki
2014-01-19 10:09                   ` Jagan Teki
2014-01-19 10:09                   ` Jagan Teki
2014-01-21  2:29                   ` Huang Shijie
2014-01-21  2:29                     ` Huang Shijie
2014-01-21  2:29                     ` Huang Shijie
2014-01-21  2:29                     ` Huang Shijie
2014-01-17  7:17           ` sourav
2014-01-17  7:17             ` sourav

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=20140119024405.GA2321@gmail.com \
    --to=shijie8@gmail.com \
    --cc=angus.clark@st.com \
    --cc=b18965@freescale.com \
    --cc=b32955@freescale.com \
    --cc=b44548@freescale.com \
    --cc=broonie@linaro.org \
    --cc=computersforpeace@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=jagannadh.teki@gmail.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=pekon@ti.com \
    --cc=shawn.guo@linaro.org \
    --cc=sourav.poddar@ti.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 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.