From: <Tudor.Ambarus@microchip.com>
To: <Claudiu.Beznea@microchip.com>, <linux@armlinux.org.uk>,
<Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
<Ludovic.Desroches@microchip.com>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: configs: at91: enable drivers for sam9x60
Date: Fri, 5 Feb 2021 10:23:56 +0000 [thread overview]
Message-ID: <e42ed693-d809-fa1d-c8bf-5264d1ff9783@microchip.com> (raw)
In-Reply-To: <56ee9cda-7943-2f5e-c068-51eff7b021b3@microchip.com>
On 2/5/21 12:12 PM, Tudor.Ambarus@microchip.com wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On 2/5/21 11:54 AM, Claudiu Beznea wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>
>> Enable drivers for sam9x60/sam9x60-ek:
>> - shutdown controller
>> - CAN
>> - AT24 EEPROM (present on SAM9X60-EK)
>> - MCP23S08 (present on SAM9X60-EK)
>> - AES, TDES, SHA
>
> Crypto IPs are present only sam9x60. Should we have them as modules?
^The ^on :)
>
>>
>> And use "make savedefconfig".
>>
>> Signed-off-by: Claudiu Beznea <claudiu.beznea@microchip.com>
>
> With or without the Crypto IPs as modules:
>
> Reviewed-by: Tudor Ambarus <tudor.ambarus@microchip.com>
>
>> ---
>> arch/arm/configs/at91_dt_defconfig | 12 +++++++-----
>> 1 file changed, 7 insertions(+), 5 deletions(-)
>>
>> diff --git a/arch/arm/configs/at91_dt_defconfig b/arch/arm/configs/at91_dt_defconfig
>> index 5f3415c743ec..e274f8c492d2 100644
>> --- a/arch/arm/configs/at91_dt_defconfig
>> +++ b/arch/arm/configs/at91_dt_defconfig
>> @@ -17,8 +17,6 @@ CONFIG_SOC_SAM9X60=y
>> # CONFIG_ATMEL_CLOCKSOURCE_PIT is not set
>> CONFIG_AEABI=y
>> CONFIG_UACCESS_WITH_MEMCPY=y
>> -CONFIG_ZBOOT_ROM_TEXT=0x0
>> -CONFIG_ZBOOT_ROM_BSS=0x0
>> CONFIG_ARM_APPENDED_DTB=y
>> CONFIG_ARM_ATAG_DTB_COMPAT=y
>> CONFIG_CMDLINE="console=ttyS0,115200 initrd=0x21100000,25165824 root=/dev/ram0 rw"
>> @@ -38,6 +36,8 @@ CONFIG_IP_PNP_BOOTP=y
>> CONFIG_IP_PNP_RARP=y
>> # CONFIG_INET_DIAG is not set
>> CONFIG_IPV6_SIT_6RD=y
>> +CONFIG_CAN=y
>> +CONFIG_CAN_AT91=y
>> CONFIG_CFG80211=y
>> CONFIG_MAC80211=y
>> CONFIG_DEVTMPFS=y
>> @@ -58,6 +58,7 @@ CONFIG_BLK_DEV_RAM=y
>> CONFIG_BLK_DEV_RAM_COUNT=4
>> CONFIG_BLK_DEV_RAM_SIZE=8192
>> CONFIG_ATMEL_SSC=y
>> +CONFIG_EEPROM_AT24=m
>> CONFIG_SCSI=y
>> CONFIG_BLK_DEV_SD=y
>> # CONFIG_SCSI_LOWLEVEL is not set
>> @@ -91,7 +92,6 @@ CONFIG_RT2800USB_UNKNOWN=y
>> CONFIG_RTL8187=m
>> CONFIG_RTL8192CU=m
>> # CONFIG_RTLWIFI_DEBUG is not set
>> -CONFIG_INPUT_POLLDEV=y
>> CONFIG_INPUT_JOYDEV=y
>> CONFIG_INPUT_EVDEV=y
>> # CONFIG_KEYBOARD_ATKBD is not set
>> @@ -111,8 +111,8 @@ CONFIG_I2C_GPIO=y
>> CONFIG_SPI=y
>> CONFIG_SPI_ATMEL=y
>> CONFIG_SPI_ATMEL_QUADSPI=y
>> +CONFIG_PINCTRL_MCP23S08=m
>> CONFIG_POWER_RESET=y
>> -# CONFIG_POWER_RESET_AT91_SAMA5D2_SHDWC is not set
>> CONFIG_POWER_SUPPLY=y
>> # CONFIG_HWMON is not set
>> CONFIG_WATCHDOG=y
>> @@ -208,7 +208,9 @@ CONFIG_NLS_UTF8=y
>> CONFIG_CRYPTO_ECB=y
>> CONFIG_CRYPTO_USER_API_HASH=m
>> CONFIG_CRYPTO_USER_API_SKCIPHER=m
>> -# CONFIG_CRYPTO_HW is not set
>> +CONFIG_CRYPTO_DEV_ATMEL_AES=y
>> +CONFIG_CRYPTO_DEV_ATMEL_TDES=y
>> +CONFIG_CRYPTO_DEV_ATMEL_SHA=y
>> CONFIG_CRC_CCITT=y
>> CONFIG_FONTS=y
>> CONFIG_FONT_8x8=y
>> --
>> 2.7.4
>>
>>
>> _______________________________________________
>> linux-arm-kernel mailing list
>> linux-arm-kernel@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-02-05 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 9:54 [PATCH] ARM: configs: at91: enable drivers for sam9x60 Claudiu Beznea
2021-02-05 10:12 ` Tudor.Ambarus
2021-02-05 10:20 ` Nicolas Ferre
2021-02-05 10:23 ` Tudor.Ambarus [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=e42ed693-d809-fa1d-c8bf-5264d1ff9783@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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).