From: Jaehoon Chung <jh80.chung@samsung.com>
To: James Hogan <james.hogan@imgtec.com>
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
linux-mmc <linux-mmc@vger.kernel.org>,
Chris Ball <cjb@laptop.org>,
Kyungmin Park <kyungmin.park@samsung.com>,
Will Newton <will.newton@imgtec.com>,
Thomas Abraham <thomas.abraham@linaro.org>,
Seungwon Jeon <tgih.jun@samsung.com>
Subject: Re: [PATCH v2 3/5] mmc: dw-mmc: add the header file for exynos specific code.
Date: Wed, 05 Sep 2012 17:33:00 +0900 [thread overview]
Message-ID: <50470E3C.5030800@samsung.com> (raw)
In-Reply-To: <5045D215.3080201@imgtec.com>
>> +static inline void exynos_set_clk_drv_sample(struct dw_mci *host,
>> + struct mmc_ios *ios)
>> +{
>> + u32 regs, ratio;
>> +
>> + regs = mci_readl(host, EXYNOS_CLKSEL);
>> + ratio = SDMMC_GET_DIV_RATIO(reg);
>> + if (!ratio) {
>> + regs &= ~SDMMC_CLK_RESET_DRV_SAMPLE;
>> + regs |= ratio;
>> + if (ios->timing == MMC_TIMING_UHS_DDR50)
>> + regs |= host->pdata->ddr_timing;
>> + else
>> + regs |= host->pdata->sdr_timing;
>
> Ah right, I see you're using them from a different patch. It feels wrong
> to platform specific data within the general platform data structure as
> it would be there unused for every other platform. Perhaps it would be
> better to have an outer exynos platform data struct which contains the
> standard one, and then use container_of to access it using the pointer
> to the inner one. Does that make sense?
I will check this. thanks for comment..
Best Regards,
Jaehoon Chung
>
>> + } else
>> + regs &= ~SDMMC_CLK_RESET_DRV_SAMPLE;
>> +
>> + mci_writel(host, EXYNOS_CLKSEL, regs);
>> +}
>> +
>> +#endif /* _EXYNOS_DW_MMC_H */
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2012-09-05 8:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-28 7:55 [PATCH v2 3/5] mmc: dw-mmc: add the header file for exynos specific code Jaehoon Chung
2012-08-28 13:37 ` Thomas Abraham
2012-08-29 2:17 ` Jaehoon Chung
2012-08-29 1:22 ` Seungwon Jeon
2012-08-29 2:12 ` Jaehoon Chung
2012-09-04 10:04 ` James Hogan
2012-09-05 8:33 ` Jaehoon Chung [this message]
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=50470E3C.5030800@samsung.com \
--to=jh80.chung@samsung.com \
--cc=cjb@laptop.org \
--cc=james.hogan@imgtec.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--cc=tgih.jun@samsung.com \
--cc=thomas.abraham@linaro.org \
--cc=will.newton@imgtec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox