From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 7/7] ARM: mxs: Add SPI driver for mx233/mx28
Date: Sun, 8 Jul 2012 07:15:32 +0200 [thread overview]
Message-ID: <201207080715.32999.marex@denx.de> (raw)
In-Reply-To: <1341712907.57646.YahooMailClassic@web124905.mail.ne1.yahoo.com>
Dear Alain-Serge Nagni,
> Hi Marek,
>
> 1) Thanks for the advice, I will remember to not top post :-)
You did it again ;-)
> 2) I spent lot of time testing your new additions to the mxs SPI driver
> and it works fine. Great job.
On what platform did you test it? And with what SPI peripherals? Can I possibly
get your proper Tested-by: line?
> Regards,
>
> Alain-Serge
>
>
> --- On Thu, 6/28/12, Marek Vasut <marex@denx.de> wrote:
>
> From: Marek Vasut <marex@denx.de>
> Subject: Re: [PATCH 7/7] ARM: mxs: Add SPI driver for mx233/mx28
> To: linux-arm-kernel at lists.infradead.org
> Cc: "Alain-Serge Nagni" <alainsergenagni@yahoo.com>, "Fabio Estevam"
> <festevam@gmail.com>, "Shawn Guo" <shawn.guo@linaro.org> Date: Thursday,
> June 28, 2012, 6:09 PM
>
> Dear Alain-Serge Nagni,
>
> > Hi Fabio and Marek,
> >
> > So I did rebuild the Kernel and UBoot to support device tree. I did
> >
> > reboot the system and this time I?m not having any kernel panic. Which is
> > a good signJ. After investigation I notice that the SSP2 node status is
> > marked ?disabled? (in the file imx28.dtsi). So there is no way based on
> > the patch that was publish to have the imx-spi driver loaded in the
> > kernel at boot time.
> > Mareck,
> >
> > I guess that you have a piece of code that you forgot to publish? If
> >not
> >
> > how can I have your SPI drive to run?
> >
> > Right now I guess that the next step would be to define the SPI node in
> >
> > the im28-evk.dts file. I will open a thread to see if anybody as a
> > solution for that. What is your take on that?
> >
> >
> >
> > Thanks guys,
> > Alain-Serge
>
> [...]
>
> Fabio already answered your question. Lemme teach you a few more rules:
> 1) Do not top post in the email conversation ;-)
> 2) About DT. You're supposed to include imx28.dtsi in your
> imx28-yourboard.dts file. Then everything that's already defined in the
> imx28.dtsi will be present in your imx28-yourboard.dts . But the key thing
> is, if you define something again, it will override the stuff already
> defined in the imx28.dtsi file. But you don't have to redefine everything,
> just redefine what you need changed.
>
> Best regards,
> Marek Vasut
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-07-08 5:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1340885853.84699.YahooMailClassic@web124903.mail.ne1.yahoo.com>
2012-06-28 22:09 ` [PATCH 7/7] ARM: mxs: Add SPI driver for mx233/mx28 Marek Vasut
2012-07-08 2:01 ` Alain-Serge Nagni
2012-07-08 5:15 ` Marek Vasut [this message]
2012-06-23 18:43 [PATCH 1/7] ARM: mxs: Move SSP register definitions into separate file Marek Vasut
2012-06-23 18:43 ` [PATCH 7/7] ARM: mxs: Add SPI driver for mx233/mx28 Marek Vasut
2012-06-25 13:22 ` Fabio Estevam
2012-06-25 13:30 ` Marek Vasut
2012-06-26 7:43 ` Shawn Guo
2012-06-26 12:22 ` Marek Vasut
2012-06-26 12:31 ` Shawn Guo
2012-06-26 12:50 ` 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=201207080715.32999.marex@denx.de \
--to=marex@denx.de \
--cc=linux-arm-kernel@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 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).