From: "Benoît Thébaudeau" <benoit.thebaudeau@advansee.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fsl_esdhc: Add no-snoop config for default init
Date: Sat, 11 Aug 2012 16:39:55 +0200 (CEST) [thread overview]
Message-ID: <192671166.2300459.1344695995863.JavaMail.root@advansee.com> (raw)
In-Reply-To: <50263749.1040101@denx.de>
Hi Stefano,
On 08/11/2012 12:43, Stefano Babic wrote:
> On 10/08/2012 23:13, Beno?t Th?baudeau wrote:
> > cfg->no_snoop was available only through custom fsl_esdhc_mmc init
> > functions.
> > Add a config options to make it available also through the default
> > init.
> >
>
> Hi Beno?t,
>
> > Signed-off-by: Beno?t Th?baudeau <benoit.thebaudeau@advansee.com>
> > Cc: Andy Fleming <afleming@gmail.com>
> > Cc: Stefano Babic <sbabic@denx.de>
> > Cc: Kim Phillips <kim.phillips@freescale.com>
> > ---
> > .../drivers/mmc/fsl_esdhc.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git u-boot-4d3c95f.orig/drivers/mmc/fsl_esdhc.c
> > u-boot-4d3c95f/drivers/mmc/fsl_esdhc.c
> > index b6c969d..21154e5 100644
> > --- u-boot-4d3c95f.orig/drivers/mmc/fsl_esdhc.c
> > +++ u-boot-4d3c95f/drivers/mmc/fsl_esdhc.c
> > @@ -597,6 +597,9 @@ int fsl_esdhc_mmc_init(bd_t *bis)
> > cfg = malloc(sizeof(struct fsl_esdhc_cfg));
> > memset(cfg, 0, sizeof(struct fsl_esdhc_cfg));
> > cfg->esdhc_base = CONFIG_SYS_FSL_ESDHC_ADDR;
> > +#ifdef CONFIG_SYS_FSL_ESDHC_NO_SNOOP
> > + cfg->no_snoop = 1;
> > +#endif
> > return fsl_esdhc_initialize(bis, cfg);
> > }
> >
>
> Using a structure to setup the controller avoids to add further
> CONFIG_
> switch. I do not find the needs to have both. Why do you need ?
fsl_esdhc_mmc_init() exists, so it should give access to all features. Moreover,
it's shorter to #define a config option than to create custom fsl_esdhc_mmc init
functions when only a single eSDHC instance is needed.
Besides that, the cache snooping feature is not available on i.MX, which means
that without CONFIG_SYS_FSL_ESDHC_NO_SNOOP or an equivalent, boards using
fsl_esdhc_mmc_init() will make esdhc_init() access a reserved bit of a reserved
register, which is not really recommended.
On i.MX, the patch could also be improved by not making this option available,
but behaving as if it were set.
Best regards,
Beno?t
next prev parent reply other threads:[~2012-08-11 14:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 21:13 [U-Boot] [PATCH] fsl_esdhc: Add no-snoop config for default init Benoît Thébaudeau
2012-08-11 10:43 ` Stefano Babic
2012-08-11 14:39 ` Benoît Thébaudeau [this message]
2012-08-11 17:25 ` Stefano Babic
2012-08-11 17:59 ` Benoît Thébaudeau
2012-08-11 21:57 ` stefano babic
2012-08-13 14:18 ` [U-Boot] [PATCH 1/2] imx: Define architecture identifier Benoît Thébaudeau
2012-08-13 14:18 ` [U-Boot] [PATCH 2/2] fsl_esdhc: Remove cache snooping for i.MX Benoît Thébaudeau
2012-08-13 14:24 ` Stefano Babic
2012-08-13 14:39 ` Benoît Thébaudeau
2012-08-13 15:16 ` Stefano Babic
2012-08-13 15:53 ` [U-Boot] [PATCH v2 " Benoît Thébaudeau
2012-08-13 17:28 ` [U-Boot] [PATCH v3 " Benoît Thébaudeau
2012-08-13 16:32 ` [U-Boot] [PATCH 1/2] imx: Define architecture identifier Otavio Salvador
2012-08-13 17:27 ` [U-Boot] [PATCH v3 1/2] mxc: " Benoît Thébaudeau
2012-09-01 7:35 ` Stefano Babic
2012-08-12 6:25 ` [U-Boot] [PATCH] fsl_esdhc: Add no-snoop config for default init Stefano Babic
2012-08-12 13:52 ` Benoît Thébaudeau
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=192671166.2300459.1344695995863.JavaMail.root@advansee.com \
--to=benoit.thebaudeau@advansee.com \
--cc=u-boot@lists.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