mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Gerlach <d-gerlach@ti.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: Tony Lindgren <tony@atomide.com>,
	Santosh Shilimkar <ssantosh@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<devicetree@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Keerthy J <j-keerthy@ti.com>, Johan Hovold <johan@kernel.org>
Subject: Re: [PATCH v4 2/2] memory: ti-emif-sram: introduce relocatable suspend/resume handlers
Date: Mon, 2 Oct 2017 10:34:18 -0500	[thread overview]
Message-ID: <0bbba52e-c7d8-647e-9b58-55cbbe236d4a@ti.com> (raw)
In-Reply-To: <20170928083827.GE23750@n2100.armlinux.org.uk>

Russell,
On 09/28/2017 03:38 AM, Russell King - ARM Linux wrote:
> On Tue, Sep 26, 2017 at 07:03:55PM -0500, Dave Gerlach wrote:
>> diff --git a/drivers/memory/emif-asm-offsets.c b/drivers/memory/emif-asm-offsets.c
>> new file mode 100644
>> index 000000000000..bdb153c9e948
>> --- /dev/null
>> +++ b/drivers/memory/emif-asm-offsets.c
>> @@ -0,0 +1,22 @@
>> +/*
>> + * TI AM33XX EMIF PM Assembly Offsets
>> + *
>> + * Copyright (C) 2016-2017 Texas Instruments Inc.
>> + *
>> + * This program is free software; you can redistribute it and/or
>> + * modify it under the terms of the GNU General Public License as
>> + * published by the Free Software Foundation version 2.
>> + *
>> + * This program is distributed "as is" WITHOUT ANY WARRANTY of any
>> + * kind, whether express or implied; without even the implied warranty
>> + * of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
>> + * GNU General Public License for more details.
>> + */
>> +#include <linux/ti-emif-sram.h>
>> +
>> +int main(void)
>> +{
>> +	ti_emif_offsets();
>> +
>> +	return 0;
>> +}
> 
> ...
> 
>> +#if defined(CONFIG_SOC_AM33XX) || defined(CONFIG_SOC_AM43XX)
>> +static inline void ti_emif_offsets(void)
>> +{
>> +	DEFINE(EMIF_SDCFG_VAL_OFFSET,
>> +	       offsetof(struct emif_regs_amx3, emif_sdcfg_val));
>> +	DEFINE(EMIF_TIMING1_VAL_OFFSET,
>> +	       offsetof(struct emif_regs_amx3, emif_timing1_val));
>> +	DEFINE(EMIF_TIMING2_VAL_OFFSET,
>> +	       offsetof(struct emif_regs_amx3, emif_timing2_val));
>> +	DEFINE(EMIF_TIMING3_VAL_OFFSET,
>> +	       offsetof(struct emif_regs_amx3, emif_timing3_val));
>> +	DEFINE(EMIF_REF_CTRL_VAL_OFFSET,
>> +	       offsetof(struct emif_regs_amx3, emif_ref_ctrl_val));
>> +	DEFINE(EMIF_ZQCFG_VAL_OFFSET,
>> +	       offsetof(struct emif_regs_amx3, emif_zqcfg_val));
>> +	DEFINE(EMIF_PMCR_VAL_OFFSET,
>> +	       offsetof(struct emif_regs_amx3, emif_pmcr_val));
>> +	DEFINE(EMIF_PMCR_SHDW_VAL_OFFSET,
>> +	       offsetof(struct emif_regs_amx3, emif_pmcr_shdw_val));
>> +	DEFINE(EMIF_RD_WR_LEVEL_RAMP_CTRL_OFFSET,
>> +	       offsetof(struct emif_regs_amx3, emif_rd_wr_level_ramp_ctrl));
>> +	DEFINE(EMIF_RD_WR_EXEC_THRESH_OFFSET,
>> +	       offsetof(struct emif_regs_amx3, emif_rd_wr_exec_thresh));
>> +	DEFINE(EMIF_COS_CONFIG_OFFSET,
>> +	       offsetof(struct emif_regs_amx3, emif_cos_config));
>> +	DEFINE(EMIF_PRIORITY_TO_COS_MAPPING_OFFSET,
>> +	       offsetof(struct emif_regs_amx3, emif_priority_to_cos_mapping));
>> +	DEFINE(EMIF_CONNECT_ID_SERV_1_MAP_OFFSET,
>> +	       offsetof(struct emif_regs_amx3, emif_connect_id_serv_1_map));
>> +	DEFINE(EMIF_CONNECT_ID_SERV_2_MAP_OFFSET,
>> +	       offsetof(struct emif_regs_amx3, emif_connect_id_serv_2_map));
>> +	DEFINE(EMIF_OCP_CONFIG_VAL_OFFSET,
>> +	       offsetof(struct emif_regs_amx3, emif_ocp_config_val));
>> +	DEFINE(EMIF_LPDDR2_NVM_TIM_OFFSET,
>> +	       offsetof(struct emif_regs_amx3, emif_lpddr2_nvm_tim));
>> +	DEFINE(EMIF_LPDDR2_NVM_TIM_SHDW_OFFSET,
>> +	       offsetof(struct emif_regs_amx3, emif_lpddr2_nvm_tim_shdw));
>> +	DEFINE(EMIF_DLL_CALIB_CTRL_VAL_OFFSET,
>> +	       offsetof(struct emif_regs_amx3, emif_dll_calib_ctrl_val));
>> +	DEFINE(EMIF_DLL_CALIB_CTRL_VAL_SHDW_OFFSET,
>> +	       offsetof(struct emif_regs_amx3, emif_dll_calib_ctrl_val_shdw));
>> +	DEFINE(EMIF_DDR_PHY_CTLR_1_OFFSET,
>> +	       offsetof(struct emif_regs_amx3, emif_ddr_phy_ctlr_1));
>> +	DEFINE(EMIF_EXT_PHY_CTRL_VALS_OFFSET,
>> +	       offsetof(struct emif_regs_amx3, emif_ext_phy_ctrl_vals));
>> +	DEFINE(EMIF_REGS_AMX3_SIZE, sizeof(struct emif_regs_amx3));
>> +
>> +	BLANK();
>> +
>> +	DEFINE(EMIF_PM_BASE_ADDR_VIRT_OFFSET,
>> +	       offsetof(struct ti_emif_pm_data, ti_emif_base_addr_virt));
>> +	DEFINE(EMIF_PM_BASE_ADDR_PHYS_OFFSET,
>> +	       offsetof(struct ti_emif_pm_data, ti_emif_base_addr_phys));
>> +	DEFINE(EMIF_PM_CONFIG_OFFSET,
>> +	       offsetof(struct ti_emif_pm_data, ti_emif_sram_config));
>> +	DEFINE(EMIF_PM_REGS_VIRT_OFFSET,
>> +	       offsetof(struct ti_emif_pm_data, regs_virt));
>> +	DEFINE(EMIF_PM_REGS_PHYS_OFFSET,
>> +	       offsetof(struct ti_emif_pm_data, regs_phys));
>> +	DEFINE(EMIF_PM_DATA_SIZE, sizeof(struct ti_emif_pm_data));
>> +
>> +	BLANK();
>> +
>> +	DEFINE(EMIF_PM_SAVE_CONTEXT_OFFSET,
>> +	       offsetof(struct ti_emif_pm_functions, save_context));
>> +	DEFINE(EMIF_PM_RESTORE_CONTEXT_OFFSET,
>> +	       offsetof(struct ti_emif_pm_functions, restore_context));
>> +	DEFINE(EMIF_PM_ENTER_SR_OFFSET,
>> +	       offsetof(struct ti_emif_pm_functions, enter_sr));
>> +	DEFINE(EMIF_PM_EXIT_SR_OFFSET,
>> +	       offsetof(struct ti_emif_pm_functions, exit_sr));
>> +	DEFINE(EMIF_PM_ABORT_SR_OFFSET,
>> +	       offsetof(struct ti_emif_pm_functions, abort_sr));
>> +	DEFINE(EMIF_PM_FUNCTIONS_SIZE, sizeof(struct ti_emif_pm_functions));
>> +}
>> +#else
>> +static inline void ti_emif_offsets(void) {}
>> +#endif
> 
> Any reason the above can't be part of emif-asm-offsets.c ?
> 

Yes that's a good point. I was focused on moving the macros and didn't think
about why I hid everything away in the header in the first place, to avoid
cluttering the global asm-offsets.c. Now that we have our own file there's no
reason for this, I will fix this and the kbuild robot issue and send v5. I can
simplify the makefile more which will avoid that build error.

Regards,
Dave

  reply	other threads:[~2017-10-02 15:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-27  0:03 [PATCH v4 0/2] memory: Introduce ti-emif-sram driver Dave Gerlach
2017-09-27  0:03 ` [PATCH v4 1/2] Documentation: dt: Update ti,emif bindings Dave Gerlach
2017-09-27  0:03 ` [PATCH v4 2/2] memory: ti-emif-sram: introduce relocatable suspend/resume handlers Dave Gerlach
2017-09-28  8:38   ` Russell King - ARM Linux
2017-10-02 15:34     ` Dave Gerlach [this message]
2017-10-03 15:14       ` Dave Gerlach
2017-09-29  6:23   ` kbuild test robot

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=0bbba52e-c7d8-647e-9b58-55cbbe236d4a@ti.com \
    --to=d-gerlach@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=j-keerthy@ti.com \
    --cc=johan@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=robh+dt@kernel.org \
    --cc=ssantosh@kernel.org \
    --cc=tony@atomide.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

all inboxes | Powered by JetHome®