From: Vince Hsu <vinceh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Allen Martin <amartin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: "swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org"
<swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 2/3] Add Tegra132 support for the cbootimage utility
Date: Tue, 15 Jul 2014 04:56:34 +0800 [thread overview]
Message-ID: <53C44402.8020803@nvidia.com> (raw)
In-Reply-To: <20140711182317.GA1730-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Hi,
On 07/12/2014 02:23 AM, Allen Martin wrote:
>> >+cbootimage_soc_config tegra132_config = {
>> >+ .init_bad_block_table = t132_init_bad_block_table,
>> >+ .set_dev_param = t132_set_dev_param,
>> >+ .get_dev_param = t132_get_dev_param,
>> >+ .set_sdram_param = t132_set_sdram_param,
>> >+ .get_sdram_param = t132_get_sdram_param,
>> >+ .setbl_param = t132_setbl_param,
>> >+ .getbl_param = t132_getbl_param,
>> >+ .set_value = t132_bct_set_value,
>> >+ .get_value = t132_bct_get_value,
>> >+ .set_data = t132_bct_set_data,
>> >+ .get_bct_size = t132_get_bct_size,
>> >+ .set_mts_info = t132_set_mts_info,
>> >+ .get_mts_info = t132_get_mts_info,
>> >+ .token_supported = t132_bct_token_supported,
>> >+
>> >+ .devtype_table = s_devtype_table_t132,
>> >+ .sdmmc_data_width_table = s_sdmmc_data_width_table_t132,
>> >+ .spi_clock_source_table = s_spi_clock_source_table_t132,
>> >+ .nvboot_memory_type_table = s_nvboot_memory_type_table_t132,
>> >+ .sdram_field_table = s_sdram_field_table_t132,
>> >+ .nand_table = 0,
>> >+ .sdmmc_table = s_sdmmc_table_t132,
>> >+ .spiflash_table = s_spiflash_table_t132,
>> >+ .device_type_table = s_device_type_table_t132,
>> >+};
>> >+
> Since Tegra132 and Tegra124 are so similar, can we reuse the Tegra124
> version of any of these to avoid the duplication?
Some of these functions like setbl_param refer to the macros/definitions
in nvboot_bct_txx.h. So maybe they look similar, actually they don't. If
we want to generalize these functions, we might have to refactor
nvboot_bct_txx.h and some more stuff. Can we leave it as is?
Thanks,
Vince
next prev parent reply other threads:[~2014-07-14 20:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 10:21 [PATCH 1/3] Rename last_bl_blk to last_blk Vince Hsu
[not found] ` <1404987710-26375-1-git-send-email-vinceh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-07-10 10:21 ` [PATCH 2/3] Add Tegra132 support for the cbootimage utility Vince Hsu
[not found] ` <1404987710-26375-2-git-send-email-vinceh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-07-11 18:23 ` Allen Martin
[not found] ` <20140711182317.GA1730-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-07-14 7:54 ` Vince Hsu
2014-07-14 20:56 ` Vince Hsu [this message]
[not found] ` <53C44402.8020803-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-07-14 22:36 ` Allen Martin
[not found] ` <20140714223659.GA13652-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-07-15 5:40 ` Vince Hsu
[not found] ` <53C4BEE3.7080604-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-07-15 21:34 ` Allen Martin
2014-07-10 10:21 ` [PATCH 3/3] Dump MTS information by bct_dump utility Vince Hsu
2014-07-10 10:26 ` [PATCH 1/3] Rename last_bl_blk to last_blk Vince Hsu
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=53C44402.8020803@nvidia.com \
--to=vinceh-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=amartin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.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 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.